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

[cachekit-renovate-bot]

This PR contains the following updates:

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

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

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

v7.1.0

Compare Source

What's Changed

Enhancements:

• Add support for mise.toml file by @​gperdomor in #​1421
• Support absolute paths in node-version-file by @​v-mahabaleshwars in #​1633

Bug fixes:

• Add Node version validation and manifest fetch retry by @​v-jitenderpalsingh in #​1580

Documentation updates:

• README.md: bump actions/checkout to latest version 7 by @​deining in #​1578
• docs: add V7 ESM migration and NODE_AUTH_TOKEN behavior change by @​v-gowridurgad in #​1593
• Fixed cache recommendation syntax by @​SubJunk in #​1603

Dependency updates:

• Update workflow pins and migrate Node matrices to modern versions by @​v-HarithaVattikuti in #​1583
• Upgrade @​actions/cache to 6.2.0 by @​philip-gai in #​1584
• Pin @​types/node to v24 by @​v-priyagupta108 in #​1585
• Override brace-expansion to 5.0.8 by @​v-priyagupta108 with @​Copilot in #​1599
• Upgrade actions/checkout from 7.0.0 to 7.0.1 by @​dependabot in #​1598
• Upgrade prettier from 3.8.4 to 3.9.6 by @​dependabot in #​1590
• Upgrade @​vercel/ncc from 0.44.0 to 0.45.0 by @​dependabot in #​1610
• Upgrade pnpm/action-setup from 6.0.9 to 6.0.10 by @​dependabot in #​1602
• Upgrade baseline-browser-mapping from 2.10.38 to 2.11.22 by @​dependabot in #​1629
• Upgrade @​types/semver from 7.7.1 to 7.8.0 by @​dependabot in #​1616
• Upgrade @​typescript-eslint/parser from 8.62.0 to 8.70.0 by @​dependabot in #​1615
• Upgrade pnpm/action-setup from 6.0.10 to 6.1.0 by @​dependabot in #​1631
• Upgrade jest-each from 30.4.1 to 30.5.2 by @​dependabot in #​1636
• Upgrade eslint-plugin-n from 18.1.0 to 18.3.0 by @​dependabot in #​1638
• Update dependencies and add license files by @​v-HarithaVattikuti in #​1642
• Upgrade eslint from 10.5.0 to 10.11.0 and package.json from 7.0.0 to 7.1.0 by @​dependabot in #​1635

New Contributors

• @​v-jitenderpalsingh made their first contribution in #​1580
• @​philip-gai made their first contribution in #​1584
• @​gperdomor made their first contribution in #​1421
• @​SubJunk made their first contribution in #​1603

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

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: (in timezone Australia/Sydney)

• Branch creation
  • "before 6am"
• 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 has been generated by Mend Renovate.

[kodus-27b]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

• Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
• Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
• Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
• Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
• API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
• Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
• Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
• Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
• Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
• Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

• Configuration used: Repository: cachekit-io/cachekit-ts/.coderabbit.yaml
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 39d1851a-32a1-4e99-bdb5-10ac703a20ec

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[kodus-27b]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the `@kody start-review` command at the root of your PR.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Providing Context (Files & MCPs)

Add these hints in your PR description (or a comment) to unlock deeper checks:

• Ticket / Acceptance Criteria: `Refs: ABC-123` (Linear/Jira/Asana/ClickUp/Trello) or a direct ticket link.
• Bugfix Validation: a Sentry/Datadog/Bugsnag event link (or paste the stack trace/error message).
• Endpoint Risk: mention the route (e.g., `POST /api/payments`) or controller/action name.
• Attach a repo file as context: use an explicit marker like `@file:docs/guide.mdx#L10-L50` (replace with your real path).
• API Contract Docs: include `@file:openapi.yaml` or `@file:swagger.json` when changing routes/schemas.
• Definition of Done / Standards: include `@file:DOD.md` or `@file:CONTRIBUTING.md` if your repo has them.
• Design System Source of Truth: include `@file:ui/index.ts` (replace with your DS entrypoint path).
• Feature Flags: include the flag key/name and `@file:flags.ts` / `@file:config.json` (and optionally the PostHog flag name).
• Edge/CDN Rules: link the Cloudflare rule/zone or describe the intended redirect/header behavior.
• Attach an MCP tool output: use `@mcp<provider|tool>` (replace with an installed MCP provider + tool, e.g., `@mcp<sentry|events.search>`).

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.