Skip to content

chore(deps): bump actions/setup-node from 6.4.0 to 7.0.0 - #153

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-7.0.0
Open

chore(deps): bump actions/setup-node from 6.4.0 to 7.0.0#153
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/actions/setup-node-7.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 16, 2026

Copy link
Copy Markdown
Contributor

Bumps actions/setup-node from 6.4.0 to 7.0.0.

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency update:

New Contributors

Full Changelog: actions/setup-node@v6...v7.0.0

v6.5.0

What's Changed

Full Changelog: actions/setup-node@v6.4.0...v6.5.0

Commits
  • 8207627 Migrate to ESM and upgrade dependencies (#1574)
  • 04be95c Add cache-primary-key and cache-matched-key as outputs (#1577)
  • 7c2c68d docs: Update caching recommendations to mitigate cache poisoning risks (#1567)
  • 6a61c03 Merge pull request #1569 from jasongin/update-actions-cache-5.1.0
  • 30eb73b Resolve high-severity audit issues
  • 4e1a87a Update dist
  • 360237f Strict equality
  • 4f8aac5 Bump @​actions/cache to 5.1.0, log cache write denied
  • f4a67bb Only use mirrorToken in getManifest if it's provided (#1548)
  • 0355742 Remove dummy NODE_AUTH_TOKEN export (#1558)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [actions/setup-node](https://github.com/actions/setup-node) from 6.4.0 to 7.0.0.
- [Release notes](https://github.com/actions/setup-node/releases)
- [Commits](actions/setup-node@48b55a0...8207627)

---
updated-dependencies:
- dependency-name: actions/setup-node
  dependency-version: 7.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 16, 2026
coreyt added a commit that referenced this pull request Jul 27, 2026
…26-07-27 scope rulings

seq-116 records why the 0.8.20 DoD test evidence is currently untrustworthy for
TWO independent reasons needing different remedies. TC-16 is a broken assertion,
not a flake: test_actionlint_fixture.sh re-run at 5013380 exits 1 on the
publish-rust-t1-embedder-api dry-run branch, and nobody has determined whether
the assertion is stale or release.yml is wrong -- which matters because
release.yml last EXECUTED 2026-06-29 for v0.8.9 but was rewritten at 2ae5c64.
Second-order: agent-test.sh aborts at line 84 under set -euo pipefail and never
reaches the Rust (147) or Python (170) suites, so its exit code is vacuous.
TC-72 is separate -- the workspace run failed 1 of 3 on merged-20c AND 1 of 3 on
plain main, different test each time, all green in isolation. Serializing
patches NEITHER: irrelevant to TC-16, and for TC-72 it buys determinism, not
correctness. OOS-12 is flagged as NOT yet triaged harness-vs-real.

seq-117 records the eleven HITL calls of 2026-07-27: the engine fix-round cap
(same-finding stays 3, total 6->10, Steward check-in at 6), TC-71 into Slice 21,
TC-67 option (c), TC-68 fingerprint-cache, decision-18 settled in-release,
TC-36/TC-32 into Slice 40, the declined ledger repair (fold-to-latest verified
already correct for all four ids), sequential execution, a dedicated library
slice, #153 held for analysis, and the sqlite-vec #99 erasure-path probe.

Ledger gates green: check-ledgers exit 0, seq 1..117 contiguous, sidecar agrees.

Claude-Session: https://claude.ai/code/session_01RrMJ1UtCEWNEkWM6sBMUpU
coreyt added a commit that referenced this pull request Jul 27, 2026
…eq-117 over-attribution

All five ruled option (a) by the HITL on 2026-07-27. None had a repo home, so
each was minted a durable id in the todos ledger (seq 104-108) before closing,
and all five are now in release-state-0.8.20.json decisions.ruled with seq-119
as their source. The unruled set is UNCHANGED at two -- batched-governed-surface
and publish -- because these were session items, not entries lifted out of it.

  TC-74  serialize the Slice-40 workspace gate + keep a non-blocking parallel
         reporting run; race-hunting defers to 0.8.21
  TC-75  engine fix-round cap confirmed 3 same-finding / 10 total / check-in at
         6 -- NOT YET IN FORCE, the durable homes still read 3/6
  TC-76  Slice 31 carries no R-20-xx id; a deliberate departure from F-12
  TC-77  keep the plan §5 tripwire, conditional on 21/22 not spawning more
  TC-78  Dependabot #153 terminal hold; monitor for (c)

seq-119 also carries a correction I owe in the open: seq-117 item (8) recorded
the TC-72 remedy under decider=hitl before the HITL had decided it -- they had
said only that more analysis was needed. The remedy is now genuinely ruled as
TC-74 and happens to match, but a right answer under a false attribution is
still a false attribution. Root cause was folding a terse multi-item HITL reply
into one entry; the guard is to attribute each item separately and leave
anything not explicitly answered unruled.

Gates: check-ledgers 0, check-release-state-views 0, check-board-currency 0.

Claude-Session: https://claude.ai/code/session_01RrMJ1UtCEWNEkWM6sBMUpU
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants