Bump actions/setup-node from 6 to 7 in the github group - #230
Open
dependabot[bot] wants to merge 1 commit into
Open
Bump actions/setup-node from 6 to 7 in the github group#230dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the github group with 1 update: [actions/setup-node](https://github.com/actions/setup-node). Updates `actions/setup-node` from 6 to 7 - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v6...v7) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
🔵 Review postedLast updated: 2026-08-01 00:08 UTC |
rtibblesbot
reviewed
Aug 1, 2026
rtibblesbot
left a comment
rtibblesbot
left a comment
Contributor
There was a problem hiding this comment.
PR #230 — dependency update review.
Package: actions/setup-node v6 → v7 (grouped update github, single member)
Semver risk: Major
Type: CI/release tooling (not a runtime dependency)
CI: All file linting failing — pre-existing repo-wide drift, not caused by this bump. All Python unit-test jobs (3.6–3.14) pass.
Changelog
- Breaking — dummy
NODE_AUTH_TOKENexport removed (#1558). v6 always rancore.exportVariable('NODE_AUTH_TOKEN', process.env.NODE_AUTH_TOKEN || 'XXXXX-...'); v7 exports it only if already set. Upstream scopes the impact: legacy Yarn Classic and older Node/npm may fail, pnpm may warn — "npm Trusted Publishing (OIDC) is not affected, since it does not useNODE_AUTH_TOKEN." - Breaking — ESM migration (#1574). No changes to inputs, outputs, or behavior;
action.ymlatv7still declaresruns.using: 'node24', same as v6. - Deprecations: none.
- Security: no CVEs for v7.0.0 itself;
@actions/cache→ 5.1.0 pulls security overrides forundiciandfast-xml-parser. Not exercised — this workflow does not enable caching. - New peer deps / required inputs: none. Two additive outputs (
cache-primary-key,cache-matched-key).
Compatibility
The only usage is .github/workflows/npm-publish.yml:15 (grep -rn setup-node .github/ returns one line). That workflow declares id-token: write # Required for npm trusted publishing (OIDC), and NODE_AUTH_TOKEN/NPM_TOKEN appear nowhere in the repo — a pure OIDC trusted-publishing setup, exactly the case upstream says is unaffected. No code changes required.
Notes
- Unverifiable by CI.
npm-publish.ymltriggers only onrelease: published, so no check in this PR runsactions/setup-node. Green CI shows the bump breaks nothing else; it is not evidence that publishing still works. The first real test is the next release — ifmake release-npmfails at the auth step, the symptom is npm failing to resolve${NODE_AUTH_TOKEN}from the generated.npmrc; revert toactions/setup-node@v6. All file lintingis unrelated. Every prek hook passes (includingactionlint); the failure is thebuildhook regeneratingjs/package.jsonfrom the setuptools-scm version (0.2.18→0.2.19). PRs #231 and #202 fail with a byte-identical diff, so it blocks every open PR and should be fixed separately by committing the regenerated file.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Ran a dependency-update review pipeline over the version bump:
- Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
- Extracted the changelog and release notes across the version range
- Assessed compatibility with this project's usage and whether any code changes are required
- Treated CI as the primary safety net
- Scaled the review depth to the update's risk
- Chose the verdict from semver risk, changelog findings, and CI status
This was referenced Aug 1, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the github group with 1 update: actions/setup-node.
Updates
actions/setup-nodefrom 6 to 7Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
8207627Migrate to ESM and upgrade dependencies (#1574)04be95cAdd cache-primary-key and cache-matched-key as outputs (#1577)7c2c68ddocs: Update caching recommendations to mitigate cache poisoning risks (#1567)6a61c03Merge pull request #1569 from jasongin/update-actions-cache-5.1.030eb73bResolve high-severity audit issues4e1a87aUpdate dist360237fStrict equality4f8aac5Bump@actions/cacheto 5.1.0, log cache write deniedf4a67bbOnly usemirrorTokeningetManifestif it's provided (#1548)0355742Remove dummy NODE_AUTH_TOKEN export (#1558)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions