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

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.56%. Comparing base (1cc3acb) to head (350a9d6).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #126   +/-   ##
=======================================
  Coverage   95.56%   95.56%           
=======================================
  Files          18       18           
  Lines        1285     1285           
=======================================
  Hits         1228     1228           
  Misses         57       57           

Flag	Coverage Δ
python	94.37% <ø> (ø)
web	99.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[njzjz-bot]

Reviewed the complete one-line workflow change. The repository CI completed successfully for this head, and I found no blocking compatibility or behavior issue with the actions/setup-node v6 → v7 update while continuing to request Node.js 22.

Agent: ChatGPT
Model: GPT-5.6 Sol
GitHub account: njzjz-bot
Reviewed head: 54f9750
Trigger: scheduled review-request monitoring

[njzjz-bot]

Re-reviewed after the head changed. The complete diff is still a single workflow update from actions/setup-node@v6 to @v7 while requesting Node.js 22. The v7 action supports this input and runs on node24; this repository does not opt into setup-node package-manager caching via packageManager/devEngines, so the v7 default caching behavior does not introduce an unexpected cache path here. All three GitHub Actions workflows for this exact head completed successfully, and pre-commit.ci is also successful. I found no high-confidence functional, compatibility, security, or test-coverage blocker.

Agent: ChatGPT
Model: GPT-5.6 Sol
GitHub account: njzjz-bot
Reviewed head: 8c8076b
Trigger: scheduled review-request monitoring

[njzjz-bot]

Re-reviewed after the head changed. The complete diff remains a single workflow update from actions/setup-node@v6 to @v7 while continuing to request Node.js 22. I checked the repository README, package/test configuration, full workflow, existing reviews/discussion, and exact-head CI. The web job exercises the updated action directly, and all three GitHub Actions workflows plus pre-commit.ci succeeded for this head. No high-confidence functional, compatibility, security, or test-coverage issue was found.

Agent: ChatGPT
Model: GPT-5.6 Sol
GitHub account: njzjz-bot
Reviewed head: c769429
Trigger: scheduled review-request monitoring

[njzjz-bot]

APPROVE

I re-reviewed the updated head. The complete diff is still the single actions/setup-node v6 to v7 change in the web-test workflow, with Node.js 22 and the existing workflow behavior otherwise unchanged. I found no functional, compatibility, security, installation, or test-coverage blocker.

All three relevant GitHub Actions workflows and pre-commit.ci are successful for this exact head.

Agent: ChatGPT
Model: GPT-5.6 Pro
GitHub account: njzjz-bot
Reviewed head: 350a9d6
Trigger: scheduled review-request monitoring