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

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
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

[github-actions]

This update standardizes the CI workflows by upgrading the Node setup action to the latest v7.0.0, ensuring consistency across build and code‐quality checks without affecting end‐user functionality.

Walkthrough

• Chore: Bumped actions/setup-node to v7.0.0 in the build workflow for improved alignment with current tooling.
• Chore: Applied the same upgrade in the code‐quality workflow to maintain uniformity across all CI processes.

_{Model: o4-mini-2025-04-16 | Prompt Tokens: 784 | Completion Tokens: 565}

[github-actions]

I have prepared a supportive review of your code with AI assistance. Please view these observations as helpful ideas rather than fixed rules. Feel welcome to adopt whatever aligns best with your approach. You remain at the helm of every choice and AI is here to back your decisions.

_{Model: o4-mini-2025-04-16 | Prompt Tokens: 1299 | Completion Tokens: 3325}

[github-actions]

Consider pinning to the semantic version tag instead of a full SHA to make future minor/patch updates easier to adopt. For example:

- name: Setup Node (PR Summary)
  uses: actions/setup-node@v7
  with:
    node-version-file: source-folder/.tool-versions
    cache: npm

[github-actions]

These two setup-node invocations share identical configuration. You could DRY this up by creating a reusable composite action (e.g. .github/actions/setup-node.yaml), then call it in both places. For example:

# .github/actions/setup-node.yaml
name: "Setup Node"
runs:
  using: composite
  steps:
    - uses: actions/setup-node@v7
      with:
        node-version-file: source-folder/.tool-versions
        cache: npm

And in your workflow:

- name: Setup Node (PR Review)
  uses: ./.github/actions/setup-node.yaml

[github-actions]

Similarly to the other workflow, switch to the semver tag for actions/setup-node for readability and easier maintenance:

- name: Setup Node
  uses: actions/setup-node@v7
  with:
    node-version-file: .tool-versions
    cache: npm

[github-actions]

It looks like you have duplicate Checkout source branch and Setup Node steps here. You can remove the redundant block or, better yet, factor out the setup into a single reusable step. This will keep the workflow concise and avoid unnecessary duplication.