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

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/setup-node	action	major	v4 -> v6

---

Release Notes

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

v6

Compare Source

v5

Compare Source

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) in timezone America/New_York, Automerge - At any time (no schedule defined).

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

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
react-shiki	Ready	Preview	Comment	Nov 1, 2025 5:26am

[changeset-bot]

⚠️ No Changeset found

Latest commit: a671ea5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[claude]

Claude finished @renovate[bot]'s task —— View job

---

PR Review: Update actions/setup-node v4 → v6

Analysis Tasks

• Read changed workflow files to understand updates
• Check repository setup and changeset configuration
• Review CLAUDE.md for repo-specific guidelines
• Assess changeset requirements for this update
• Evaluate code quality and potential issues
• Provide comprehensive review feedback

📋 Review Summary

This PR updates actions/setup-node from v4 to v6 across two GitHub workflow files. The changes are minimal and well-targeted.

✅ Changeset Assessment

No changeset required for this update because:

• This is a CI/build infrastructure dependency, not a package source dependency
• The change affects only GitHub Actions workflow configuration (.github/workflows/)
• It does not modify the published package code, API surface, or functionality
• Per the changeset-bot comment, this correctly identifies no version bump is needed

The changeset requirement in the direct prompt applies to "package source" updates, which this is not.

🔍 Code Quality & Changes Analysis

Files Changed:

• .github/workflows/build.yml:19 - Updated setup-node from v4 → v6
• .github/workflows/release.yaml:26 - Updated setup-node from v4 → v6

Code Quality: ✅ Excellent

• Changes are minimal and precisely targeted
• Consistent application across both workflow files
• No breaking changes to workflow logic
• Maintains existing configuration (node versions, cache settings)

🔒 Security & Performance

Security: ✅ Low Risk

• Moving to a newer major version of a trusted GitHub Action
• actions/setup-node is maintained by GitHub and widely adopted
• Major version bumps in GitHub Actions typically include security improvements

Performance: ✅ Neutral to Positive

• Newer action versions often include performance optimizations
• No expected negative performance impact
• Caching behavior preserved with cache: pnpm

🧪 Testing & Compatibility

Node.js Compatibility: ✅ Maintained

• Build workflow tests Node.js 18, 20, 22 (unchanged)
• Release workflow uses Node.js 22 (unchanged)
• actions/setup-node v6 supports all these versions

No Test Updates Required:

• Infrastructure change only
• Existing tests remain valid

🚀 Recommendations

1. Approve and merge - This is a straightforward infrastructure update
2. Monitor CI - Verify workflows continue functioning as expected
3. No additional changes needed - The update is complete and appropriate

📝 Additional Notes

• The Renovate configuration appears properly set up for automated dependency updates
• This follows good practices for keeping CI dependencies current
• The major version jump (v4→v6) suggests significant improvements in the action

Overall Assessment: ✅ Ready to merge