chore(deps): update actions/setup-node action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	major	v6.4.0 → v7.0.0

---

Release Notes

actions/setup-node (actions/setup-node)

v7.0.0

Compare Source

What's Changed

Enhancements:

• Add cache-primary-key and cache-matched-key as outputs by @​gowridurgad in #​1577
• Migrate to ESM and upgrade dependencies by @​gowridurgad in #​1574

Bug fixes:

• Remove dummy NODE_AUTH_TOKEN export by @​gowridurgad in #​1558
• Only use mirrorToken in getManifest if it's provided by @​deiga in #​1548

Documentation updates:

• Add documentation for publishing to npm with Trusted Publisher (OIDC) by @​chiranjib-swain in #​1536
• docs: Update restore-only cache documentation by @​priya-kinthali in #​1550
• docs: Update caching recommendations to mitigate cache poisoning risks by @​chiranjib-swain in #​1567

Dependency update:

• Upgrade @​actions/cache to 5.1.0, log cache write denied by @​jasongin in #​1569

New Contributors

• @​chiranjib-swain made their first contribution in #​1536
• @​deiga made their first contribution in #​1548
• @​jasongin made their first contribution in #​1569

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

v7

Compare Source

v6.5.0

Compare Source

What's Changed

• Update @​actions/cache to 5.1.0 and add security overrides for undici and fast-xml-parser by @​HarithaVattikuti in #​1579

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6e2cc77

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[cursor]

Risk: low. Cursor Bugbot was not present on this PR; evaluated without that signal. Single workflow dependency bump (actions/setup-node v6→v7) with no approval-policy requirements — approved. No reviewers assigned.

  

_{Sent by Cursor Approval Agent: Pull Request Router and Approver}

[greptile-apps]

PR author is in the excluded authors list.

[devin-ai-integration]

Devin Review found 1 potential issue.

[devin-ai-integration]

🔍 Verify setup-node v7 still supports Node 22 / this input set

This bump is the only setup-node usage in the repo (.github/workflows/governance-enforce.yml:31), so there is no consistency gap with other workflows. The one thing worth confirming externally is that the v7 major of actions/setup-node still accepts the node-version: "22" input and did not change defaults (e.g. caching or registry handling) that this job relies on when writing its own .npmrc at .github/workflows/governance-enforce.yml:37. Major-version bumps of actions are the usual place such breaking input/behavior changes land, and the pinned SHA cannot be validated from the repo alone.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[macroscopeapp]

Approvability

Verdict: Needs human review

This CI dependency update bumps actions/setup-node from v6 to v7. The changed file is owned by wave-av/streaming-team, and there's an unresolved comment about verifying v7 compatibility with the current Node 22 configuration. The designated code owners should verify the major version bump doesn't break the workflow.

No code changes detected at 6a5e9c2. Prior analysis still applies.

^{You can customize Macroscope's approvability policy. Learn more.}

[codeant-ai]

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.