chore(ci): Add Node.js 25 to test matrix

[yamadashy]

Added Node.js 25.x to the CI test matrix to ensure compatibility with the latest Node.js version.

This change updates both the test and build-and-run jobs in the CI workflow to include Node.js 25.x alongside the existing versions (20.x, 22.x, 24.x).

Changes

• Updated .github/workflows/ci.yml to add 25.x to the node-version matrix in the test job
• Updated .github/workflows/ci.yml to add 25.x to the node-version matrix in the build-and-run job

Testing

Each job will now run across 12 combinations:

• 3 operating systems (Ubuntu, Windows, macOS)
• 4 Node.js versions (20.x, 22.x, 24.x, 25.x)

Checklist

• Run npm run test
• Run npm run lint

[cloudflare-workers-and-pages]

Deploying repomix with    Cloudflare Pages

Latest commit:	d600b81
Status:	✅  Deploy successful!
Preview URL:	https://d053d126.repomix.pages.dev
Branch Preview URL:	https://chore-ci-add-node-25.repomix.pages.dev

View logs

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[coderabbitai]

Walkthrough

The pull request extends the Node.js version matrix in GitHub Actions CI workflow jobs by adding Node 25.x support. The matrix is expanded from [20.x, 22.x, 24.x] to [20.x, 22.x, 24.x, 25.x] across test and build-related jobs with no algorithmic or control-flow modifications.

Changes

Cohort / File(s)	Change Summary
CI Workflow Node Matrix Update \.github/workflows/ci\.yml	Added Node 25.x to the Node.js version matrix for test and build jobs, expanding supported versions from three to four entries

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Single file modification with homogeneous, repetitive change (one-line matrix expansion)
• No logic, control flow, or configuration structure alterations

Possibly related PRs

• fix(package): Fix secretlint command #124: Introduced multi-OS and Node.js version matrices to the CI workflow, establishing the foundational matrix-driven test structure
• chore(ci): Remove end-of-life Node.js versions 21 and 23 from CI matrix #819: Modified Node.js version matrix entries to remove end-of-life versions, representing maintenance of supported versions
• chore: drop node 16 as it is EOL #225: Updated Node.js version entries in CI workflow matrices, similar pattern of version support adjustment

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely summarizes the main change: adding Node.js 25 to the CI test matrix.
Description check	✅ Passed	The description includes a clear summary, detailed changes, testing information, and the required checklist template sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/ci-add-node-25

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3269d42 and d600b81.

📒 Files selected for processing (1)

• .github/workflows/ci.yml (2 hunks)

⏰ 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). (13)

• GitHub Check: Agent
• GitHub Check: Build and run (windows-latest, 24.x)
• GitHub Check: Build and run (macos-latest, 25.x)
• GitHub Check: Build and run (windows-latest, 22.x)
• GitHub Check: Build and run (windows-latest, 20.x)
• GitHub Check: Build and run (windows-latest, 25.x)
• GitHub Check: Build and run (ubuntu-latest, 25.x)
• GitHub Check: Build and run with Bun (windows-latest, latest)
• GitHub Check: Test (windows-latest, 25.x)
• GitHub Check: Test (windows-latest, 22.x)
• GitHub Check: Test with Bun (windows-latest, latest)
• GitHub Check: claude-review
• GitHub Check: Cloudflare Pages

🔇 Additional comments (1)

.github/workflows/ci.yml (1)

137-137: Approve Node.js 25.x matrix expansion.

The addition of Node.js 25.x to both the test and build-and-run job matrices is a solid forward-compatibility measure. The changes are consistent across both jobs and maintain ascending version order. This will ensure the project is tested against the latest Node.js releases while retaining coverage of earlier LTS versions (20.x, 22.x, 24.x).

Optional operational note: Monitor the additional CI runs (now 12 per matrix job instead of 9) for any unexpected build time impacts, especially on macOS and Windows runners which can have longer queue times. If CI duration becomes a concern, consider conditionally running full matrix tests only on main branch pushes or scheduled intervals.

Also applies to: 218-218

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (main@3269d42). Learn more about missing BASE report.
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #941   +/-   ##
=======================================
  Coverage        ?   89.62%           
=======================================
  Files           ?      111           
  Lines           ?     7839           
  Branches        ?     1501           
=======================================
  Hits            ?     7026           
  Misses          ?      813           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 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.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[claude]

Code Review Summary

This PR adds Node.js 25.x to the CI test matrix to ensure compatibility with the latest Node.js version. Overall, this is a good change that improves test coverage and future-proofs the project. The implementation is straightforward and correct.

✅ Strengths

• Proactive compatibility testing: Adding Node.js 25 before widespread adoption is excellent forward-thinking
• Consistent application: The change is correctly applied to both test and build-and-run jobs
• Minimal risk: The change is isolated to CI configuration with no code changes
• Well-documented: The PR description clearly explains the changes and testing impact
• Follows commit conventions: Commit message follows Conventional Commits format with appropriate scope

📋 Code Quality

Positive aspects:

• Clean, minimal diff showing only necessary changes
• Symmetric changes across both job matrices
• No breaking changes to existing tests
• Maintains consistency with existing version format (X.x)

Observations:

• The .tool-versions file specifies nodejs 24.0.1, which is appropriate as it represents the development standard
• The test matrix now covers 4 Node.js versions across 3 operating systems = 12 combinations per job

🔍 Potential Issues & Considerations

1. Node.js 25 Release Status ⚠️

Node.js 25 appears to be very recently released or in pre-release status. Consider:

• Is Node.js 25.x officially released and stable? Or is it a pre-release/beta?
• If it's pre-release, tests might fail or behave unexpectedly
• The minimum supported version in package.json is >=20.0.0, which is appropriate

Recommendation: Verify Node.js 25 is officially released. If it's still in beta/RC, consider using continue-on-error: true for this version initially.

2. CI Resource Impact ℹ️

• Before: 9 test combinations (3 OS × 3 versions) = 18 jobs total
• After: 12 test combinations (3 OS × 4 versions) = 24 jobs total
• This represents a 33% increase in CI time and resource usage

Considerations:

• GitHub Actions free tier has monthly limits
• If CI becomes too slow, consider reducing coverage for older versions
• Monitor the impact on PR feedback time

3. Version Support Policy 📚

The project should consider documenting a clear Node.js version support policy:

• Which versions are officially supported?
• When to drop support for older versions?
• Testing vs. support distinction

Suggestion: Update README.md or documentation to clarify the supported Node.js versions.

4. Dependency Compatibility 🔍

Some dependencies may not yet support Node.js 25:

• tree-sitter-wasms, tiktoken, and other native modules
• TypeScript compilation might surface new issues
• Consider monitoring the test runs closely after merge

🎯 Premortem Analysis: Potential Failure Scenarios

Scenario 1: Node.js 25 Incompatibilities

Risk: Native dependencies or packages may not support Node.js 25
Likelihood: Medium (new major version often has compatibility issues)
Impact: CI failures, blocking PRs
Mitigation:

• Monitor first test runs closely
• If failures occur, add continue-on-error: true temporarily
• Report issues to upstream dependencies

Scenario 2: Breaking Changes in Node.js 25

Risk: Node.js 25 may include breaking changes affecting the codebase
Likelihood: Low-Medium (Node.js maintains good backward compatibility)
Impact: Test failures, potential code changes needed
Mitigation:

• Review Node.js 25 release notes for breaking changes
• Fix any issues discovered during testing
• Consider if code changes are needed

Scenario 3: Increased CI Time and Costs

Risk: 33% more CI jobs could slow down feedback loop
Likelihood: High (mathematical certainty)
Impact: Slower PR reviews, potential GitHub Actions quota issues
Mitigation:

• Monitor CI duration and adjust if needed
• Consider running Node.js 25 tests only on main branch initially
• Future consideration: drop Node.js 20 when 26 is released

Scenario 4: Flaky Tests on Node.js 25

Risk: Tests pass locally but are flaky on Node.js 25 in CI
Likelihood: Low-Medium
Impact: Intermittent CI failures, developer frustration
Mitigation:

• Investigate and fix any flaky tests promptly
• Use test retries if necessary
• Consider isolating problematic tests

💡 Recommendations

Before Merge:

1. ✅ Verify Node.js 25 is officially released (not pre-release)
2. ⚠️ Consider adding continue-on-error: true initially for Node.js 25 to prevent blocking other tests
3. 📝 Update documentation to reflect supported Node.js versions

After Merge:

1. 👀 Monitor CI runs closely for any Node.js 25-specific failures
2. 📊 Track CI duration to ensure it remains acceptable
3. 🔄 Consider long-term version support strategy

Future Considerations:

• When Node.js 26 is released, consider dropping 20.x support (maintain 4 versions)
• Consider matrix configuration to test latest versions more frequently
• Document version support policy in CONTRIBUTING.md

✨ Conclusion

Verdict: ✅ Approve with minor considerations

This is a valuable addition that ensures compatibility with the latest Node.js release. The implementation is correct, and the change is well-scoped. The main considerations are around Node.js 25's release status and CI resource usage, which can be monitored post-merge.

Confidence Level: High - This is a straightforward CI configuration change with low risk.

[Copilot]

Pull Request Overview

This PR adds Node.js 25.x to the CI test matrix to ensure compatibility with the latest Node.js version. The project currently requires Node >= 20.0.0 and tests against versions 20.x, 22.x, and 24.x.

• Adds Node.js 25.x to the test matrix for the test job
• Adds Node.js 25.x to the test matrix for the build-and-run job