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 → v7

---

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 9am on monday"
• Automerge
  • At any time (no schedule defined)

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

♻ Rebasing: Whenever PR becomes conflicted, 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.

[ryanio]

Approving. Checks green, and the v7 stability window has passed.

The major bump is driven by setup-node's internal ESM migration, not by any input change — node-version, node-version-file, cache and registry-url all keep their current semantics, so no edits are needed beyond the version.

The one item worth a look was "Remove dummy NODE_AUTH_TOKEN export" (actions/setup-node#1558), since npm-publish.yml sets registry-url and that workflow only runs on release: published — it never gets exercised by PR CI. Checked the upstream rationale:

While this didn't break OIDC flows, it could corrupt the user's .npmrc by injecting a non-functional token value into the environment, potentially causing confusing behavior during OIDC publish. This PR removes the dummy fallback and only exports NODE_AUTH_TOKEN when the user has explicitly set it.

This repo publishes via npm Trusted Publishing — permissions: id-token: write plus npm publish --provenance, with no NODE_AUTH_TOKEN or NPM_TOKEN anywhere in the workflow. So dropping the dummy is neutral-to-beneficial here: nothing depended on the placeholder, and the .npmrc written alongside the OIDC exchange is now cleaner.

The three main.yaml jobs did run on v7 in this PR's own CI and passed, which covers the node-version: 24.x + cache: npm path directly. npm-publish.yml stays unverified until a release is cut, so that is the thing to keep an eye on next publish.