chore(deps): bump actions/setup-node from 6 to 7 in the actions group

[dependabot]

Bumps the actions group with 1 update: actions/setup-node.

Updates actions/setup-node from 6 to 7

Release notes

Sourced from actions/setup-node's releases.

v7.0.0

What's Changed

Enhancements:

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

Bug fixes:

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

Documentation updates:

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

Dependency update:

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

New Contributors

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

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

v6.5.0

What's Changed

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

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

v6.4.0

What's Changed

Dependency updates:

• Upgrade @​actions dependencies by @​Copilot in actions/setup-node#1525
• Update Node.js versions in versions.yml and bump package to v6.4.0 by @​priya-kinthali in actions/setup-node#1533

New Contributors

• @​Copilot made their first contribution in actions/setup-node#1525

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

v6.3.0

What's Changed

Enhancements:

• Support parsing devEngines field by @​susnux in actions/setup-node#1283

... (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 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[labro-bot]

Labro picking up. Assigning to opencode:opencode/big-pickle.

[labro-bot]

Dependency review: actions/setup-node v6 → v7

Semver risk: major — a major-bump GitHub Action, which normally warrants deeper scrutiny. That said, v7.0.0 contains no breaking input changes: node-version, cache, and cache-dependency-path (the only inputs this workflow uses) are all still present in the v7 action.yml. The runtime moves to node24, which GitHub-hosted ubuntu-latest runners fully support (the repo uses actions/checkout@v7 + the same runners already, per #49).

Changes in this release:

• Migrate to ESM and upgrade dependencies (#1574)
• New outputs: cache-primary-key, cache-matched-key (additive, non-breaking)
• Bug fixes: remove dummy NODE_AUTH_TOKEN export (#1558), only use mirrorToken in getManifest if provided (#1548)
• @actions/cache upgraded to 5.1.0; v6.5.0 (in-range) shipped security overrides for high-severity undici / fast-xml-parser audit findings
• No CVE/advisory triggered this PR — it is a routine group bump, not a security update

Lock file: clean — single-file change (.github/workflows/ci-dashboard.yml, +1/−1). No lock file touched (GitHub Actions deps have no lockfile).

Prior pins: none found — git log shows only routine Dependabot bumps (setup-node 4→6 in #38, checkout 6→7 in #49). No manual pin or comment referencing setup-node exists.

Conflict check: N/A for GitHub Actions (no package resolver). Equivalent check performed: confirmed the v7 tag resolves to v7.0.0 and that the v7 action.yml accepts every input this workflow passes (node-version: 22, cache: npm, cache-dependency-path: dashboard/package-lock.json). No compatibility risk detected.

CI: passing, with one caveat — the green ci check is ci-python.yml (runs on all PRs). The workflow this PR modifies (ci-dashboard.yml) is path-filtered to dashboard/** and did not run on this branch, so setup-node@v7 won't actually be exercised until the next dashboard push/PR after merge. Low risk given the verified, backward-compatible inputs.

Recommendation: ✅ Safe to merge — routine, compatible major bump. First dashboard CI run after merge will serve as the real-world smoke test.