Skip to content

chore(deps): bump actions/setup-node from 6 to 7 - #6976

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

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

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps actions/setup-node from 6 to 7.

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

v6.4.0

What's Changed

Dependency updates:

New Contributors

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

v6.3.0

What's Changed

Enhancements:

... (truncated)

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 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
...

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 15, 2026
@copy-pr-bot

copy-pr-bot Bot commented Jul 15, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@github-code-quality

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage remains at 96%, unchanged from the main branch.


Code Coverage is in Public Preview. Learn more and provide us with your feedback.

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — Blocking findings reported

Advisor assessment: Blockers require maintainer review
Next action: Review the blockers below.
Findings: 1 blocker · 1 warning · 0 suggestions

Model lanes

  • GPT-5.6 Terra (primary): Completed · high confidence · 1 blocker · 1 warning · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 1 suggestion
  • Model comparison: normalized findings differ; normalized E2E selections match; Nemotron reported 1 fewer blocker, 1 fewer warning, 1 more suggestion.

Nemotron output stays in workflow artifacts and does not change the assessment above.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: cloud-onboard, credential-sanitization, security-posture

Blockers

PRA-2 Blocker — Update the workflow contract for the new setup-node revision

  • Location: test/pr-workflow-contract.test.ts:74
  • Category: correctness
  • Problem: The patch changes the installer-hash workflow parser runtime to setup-node SHA `820762786026740c76f36085b0efc47a31fe5020`, while this checked-in contract still defines the required setup-node action as the old SHA `48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e` and asserts it for that workflow.
  • Impact: The repository's workflow contract test deterministically fails against the changed workflow, preventing the intended action upgrade from satisfying its checked-in contract.
  • Fix: Update `trustedSetupNodeAction` and any associated expected version metadata in `test/pr-workflow-contract.test.ts` to the reviewed immutable v7 SHA used by the workflow.
  • Verification: Inspect `test/pr-workflow-contract.test.ts` lines 74 and 293 together with `.github/workflows/installer-hash-check.yaml` line 34; the expected and actual `actions/setup-node` strings currently differ.
  • Test coverage: The existing `test/pr-workflow-contract.test.ts` assertion at line 293 is the regression coverage; update its expected immutable v7 revision so it continues to reject unintended action changes.
  • Evidence: `.github/workflows/installer-hash-check.yaml:34` now uses `actions/setup-node@820762786026740c76f36085b0efc47a31fe5020`. `test/pr-workflow-contract.test.ts:74` retains `trustedSetupNodeAction = "actions/setup-node@48b55a011bda9f5d6aeb4c2d9c7362e8dae4041e"`. `test/pr-workflow-contract.test.ts:293` asserts the parser runtime setup action equals `trustedSetupNodeAction`.
1 warning · 0 suggestions

Warnings

Warnings do not block.

PRA-1 Warning — Pin setup-node to an immutable revision

  • Location: .github/workflows/commit-lint.yaml:26
  • Category: scope
  • Problem: This workflow changes the Node setup action from the floating `actions/setup-node@v6` tag to the floating `@v7` tag. `.github/workflows/e2e-branch-validation.yaml:225` makes the same mutable-tag change, while the other changed workflows use a full immutable setup-node SHA.
  • Impact: A later retarget of the `v7` tag can alter code executed in pull-request workflows without a reviewed repository change. In `e2e-branch-validation.yaml`, the action runs before credential-bearing branch-validation steps.
  • Recommendation: Replace both floating `actions/setup-node@v7` references with the reviewed immutable commit SHA for v7 and retain an accurate version comment.
  • Verification: Read `.github/workflows/commit-lint.yaml:26` and `.github/workflows/e2e-branch-validation.yaml:225` and confirm their setup-node `uses:` values are full 40-character commit SHAs matching the reviewed v7 release.
  • Test coverage: Existing workflow pinning contract coverage should assert that all `actions/setup-node` references, including these two workflows, use immutable 40-character SHAs.
  • Evidence: `.github/workflows/commit-lint.yaml:25` changes `uses: actions/setup-node@v6` to `uses: actions/setup-node@v7`. `.github/workflows/e2e-branch-validation.yaml:194` makes the same floating-tag change. The remaining setup-node changes in this PR use immutable SHA `820762786026740c76f36085b0efc47a31fe5020`. Current repository search locates `actions/setup-node@v7` at `.github/workflows/commit-lint.yaml:26` and `.github/workflows/e2e-branch-validation.yaml:225`. The ledger previously cited lines 25 and 194 for these same changed references.

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

@dependabot @github

dependabot Bot commented on behalf of github Jul 16, 2026

Copy link
Copy Markdown
Contributor Author

Dependabot attempted to update this pull request, but because the branch dependabot/github_actions/actions/setup-node-7 is protected it was unable to do so.

@apurvvkumaria

Copy link
Copy Markdown
Collaborator

Superseded by #7161, which preserves the original Dependabot update with co-author credit while updating every current workflow reference, pinning the official v7.0.0 commit immutably, and adding the current workflow-boundary coverage. Thank you to Dependabot for identifying and opening the dependency update.

@dependabot @github

dependabot Bot commented on behalf of github Jul 18, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/github_actions/actions/setup-node-7 branch July 18, 2026 21:43
apurvvkumaria added a commit that referenced this pull request Jul 25, 2026
<!-- markdownlint-disable MD041 -->
## Summary

Updates every production `actions/setup-node` reference from v6 to the
official immutable v7.0.0 commit. This is a fresh, maintainable
replacement for #6976; the original Dependabot author is credited
throughout the branch history.

## Changes

- Pin all 44 production `actions/setup-node` references to
`820762786026740c76f36085b0efc47a31fe5020` (`v7.0.0`).
- Preserve the trusted `prepare-e2e` boundary by pinning all 78
consumers to the first commit in this branch, whose action content
already contains the v7 update.
- Update workflow-boundary constants and tests so mutable or stale
setup-node pins remain rejected.
- Keep the bootstrap history intact because later commits intentionally
reference the first commit as an immutable action source.

## Type of Change

- [x] Code change (feature, bug fix, or refactor)
- [ ] Code change with doc updates
- [ ] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)

## Quality Gates
<!-- Check one tests line and one docs line. Check other lines when
applicable. Add every requested justification or approval reference. -->
- [x] Tests added or updated for changed behavior
- [ ] Existing tests cover changed behavior — justification:
- [ ] Tests not applicable — justification:
- [ ] Docs updated for user-facing behavior changes
- [x] Docs not applicable — justification: this changes internal GitHub
Actions pins and workflow-boundary tests only; no user-facing behavior
or documentation surface changes.
- [x] Sensitive paths changed (security, policy, credentials, preflight,
onboarding, inference, runner, sandbox, or messaging)
- [x] Sensitive-path review completed or maintainer-approved waiver
recorded — reviewer/approval link/justification: independent review
verified the official signed v7.0.0 source, immutable self-reference,
trusted-checkout boundary, YAML validity, and absence of permission or
secret-handling changes.
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Verification
<!-- Check each applicable item only when supported by the requested
evidence. Run targeted tests once per relevant change set and rerun
after later edits or hook autofixes that can affect the tested behavior.
Do not rerun hook-covered checks. -->
- [x] PR description includes a `Signed-off-by:` line and every commit
appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run check:diff` passed when hooks were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — 317 workflow/security tests passed
across 17 files at the pin-complete head; after syncing the current-main
sandbox permission fix, exact-head validation passed 89/89 tests across
6 workflow and sandbox-contract files. All changed YAML parsed in the
pre-commit hook and `git diff --check` is clean.
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result: not run; focused workflow
and security-contract coverage was used for this pin-only change.
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only)
- [ ] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)

## Documentation Writer Review
- [x] Documentation writer subagent reviewed the completed changes
- Result: `no-docs-needed`
- Evidence: GitHub Actions dependency pins and workflow-contract tests
changed; no user-facing behavior or documentation surface changed.
Pin-complete validation passed 317/317 tests across 17 files, and
exact-head post-sync validation passed 89/89 tests across 6 files.
- Agent: Codex Desktop
<!-- docs-review-head-sha: 8ffb799 -->
<!-- docs-review-agents-blob-sha: 9c9b36d -->

---
Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Updated CI and E2E workflows (including shared composite actions) to
use a refreshed, pinned `actions/setup-node` reference aligned with
v7.0.0 for improved consistency and stronger supply-chain pinning.
* Refreshed trusted E2E workspace preparation action pins where
applicable.

* **Tests**
* Updated workflow boundary and integrity tests to match the new pinned
`actions/setup-node` references and the refreshed trusted E2E
preparation action pins.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Apurv Kumaria <akumaria@nvidia.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.

1 participant