chore: bump versions

[iiio2]

node v24 is not lts and prettierignore by default ignores node_modules.

Summary by CodeRabbit

• Chores
  • Upgraded development environment to Node.js 24 across CI/CD pipelines and local configuration
  • Updated GitHub Actions workflow tools to latest versions for improved stability
  • Adjusted code formatting configuration

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
v4	Ready	Preview	Comment	Oct 30, 2025 4:01pm

[coderabbitai]

Walkthrough

This PR updates GitHub Actions workflow versions (checkout v4→v5, setup-node v4→v6), bumps Node.js version from 22 to 24 across configuration files, and modifies prettier ignore patterns to exclude pnpm-lock.yaml instead of node_modules.

Changes

Cohort / File(s)	Summary
GitHub Actions Workflows .github/workflows/ci.yml, .github/workflows/test.yml	Upgrade checkout action from v4 to v5 and setup-node action from v4 to v6; test.yml additionally bumps Node.js runtime version from 22 to 24
Node.js Configuration .nvmrc	Bump Node.js version from 22 to 24
Prettier Configuration .prettierignore	Replace node_modules ignore entry with pnpm-lock.yaml; backup/ and *.md patterns remain unchanged

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• All changes are straightforward version bumps and configuration updates with minimal logic impact
• Version updates are consistent across workflows and configuration files
• Prettier ignore pattern change is a single, localized modification

Poem

🐰 Versions hop up with Node's mighty leap,
From twenty-two to twenty-four deep.
Actions dance—v5 and v6 align,
While Prettier skips the lock files fine.
All systems set for smoother builds anew!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title "chore: bump versions" is directly related to the changeset's main objective, which involves bumping multiple versions including Node.js (from 22 to 24) in .nvmrc and workflow files, and GitHub Actions dependencies (checkout v4→v5, setup-node v4→v6). The title is somewhat broad in that it doesn't specify which versions are being bumped, but this is appropriate given the scope of changes across multiple configuration files. A developer scanning the commit history would clearly understand that this PR updates various version dependencies without requiring excessive detail in the title itself.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/bump-versions

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c8c4e52 and ad2cd05.

📒 Files selected for processing (4)

• .github/workflows/ci.yml (1 hunks)
• .github/workflows/test.yml (1 hunks)
• .nvmrc (1 hunks)
• .prettierignore (0 hunks)

💤 Files with no reviewable changes (1)

• .prettierignore

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (3)

.nvmrc (1)

1-1: Verify Node.js 24 is an intentional choice given its non-LTS status.

Node.js 24 is not LTS, which means it has a shorter support window and will reach end-of-life sooner than LTS versions (e.g., Node 22). The PR notes this, but this choice warrants verification to ensure it aligns with the project's support and stability requirements.

If LTS stability is preferred, consider using Node 22 (current LTS) instead.

.github/workflows/ci.yml (1)

20-20: Verify GitHub Actions versions are compatible and current.

The workflow upgrades actions from v4 to v5 (checkout) and v4 to v6 (setup-node)—these are major version jumps. Confirm that:

1. actions/checkout@v5 is compatible with current workflows and introduces no breaking changes
2. actions/setup-node@v6 works with Node 24 and respects .nvmrc for version resolution
3. Both actions are currently maintained and up-to-date

You can verify the latest versions and changelog on the respective GitHub repositories:

• https://github.com/actions/checkout
• https://github.com/actions/setup-node

Also applies to: 22-22

.github/workflows/test.yml (1)

14-14: Verify actions/setup-node@v6 with Node 24.

The test workflow explicitly pins Node 24 (non-LTS) and uses actions/setup-node@v6. Confirm that setup-node@v6 properly supports Node 24 and that this version bump from v4 introduces no breaking changes to your CI/CD logic.

Additionally, the non-LTS Node 24 concern (flagged in .nvmrc review) applies here as well. Verify this aligns with project stability and support requirements.

Also applies to: 22-22, 24-24

---

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 and usage tips.}