Bump Node.js version to 24 in CI configuration files

[marcelorodrigo]

Summary by CodeRabbit

• Chores
  • Updated Node.js runtime version from 22 to 24 across CI/CD workflows to leverage latest runtime features and performance improvements.

[coderabbitai]

Walkthrough

Node.js version updated from 22 to 24 across three GitHub Actions workflow files (ci.yml, publish.yml, and update-indexes.yml). No other changes to workflow steps or control flow.

Changes

Cohort / File(s)	Summary
Node.js version updates .github/workflows/ci.yml, .github/workflows/publish.yml, .github/workflows/update-indexes.yml	Updated Node.js version from 22 to 24 in the setup node step across all three workflows

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Rationale: Repetitive configuration updates across three files with no logic changes, control flow modifications, or behavioral implications.

Poem

🐰 A version bump, so swift and clean,
From twenty-two to twenty-four seen,
Three workflows dance in harmony,
Node.js flows with fewest worry,
Hopping forward cheerfully! 🚀

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: updating Node.js version from 22 to 24 across all CI workflow files.
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 node24

---

📜 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 df49738 and 10443c3.

📒 Files selected for processing (3)

• .github/workflows/ci.yml (1 hunks)
• .github/workflows/publish.yml (1 hunks)
• .github/workflows/update-indexes.yml (1 hunks)

🔇 Additional comments (3)

.github/workflows/publish.yml (1)

28-32: Verify Node.js 24 compatibility with project dependencies and code.

Node.js 24 has officially entered Long-Term Support (LTS) as of version 24.11.0 ("Krypton") and will continue receiving maintenance through April 2028. However, the transition from Node.js 22 LTS to Node.js 24 LTS introduces breaking changes including OpenSSL 3.5 with stricter cryptographic standards, and npm 11.0.0 includes a breaking change where --ignore-scripts no longer runs for the prepare lifecycle script.

Before deploying, ensure:

• All project dependencies are compatible with Node.js 24
• Project code doesn't use deprecated APIs (e.g., fs.F_OK, util.log(), tls.createSecurePair())
• CI/CD pipeline passes with Node.js 24

.github/workflows/ci.yml (1)

14-19: Ensure all tests pass with Node.js 24.

This CI workflow includes test execution (line 23: pnpm test), which is valuable for catching compatibility issues early. Node.js 24 includes improved argument validation in Buffer APIs, better error propagation in stream operations, and changes to readline behavior. Monitor test output for any failures related to these changes.

.github/workflows/update-indexes.yml (1)

19-24: Validate index update behavior on Node.js 24.

This workflow automatically updates and commits indicadores.json, making it higher risk for silent behavioral changes. Ensure the pnpm update-indexes script produces identical results on Node.js 24 versus Node.js 22. Consider running this job on Node.js 22 once more to compare outputs, or add a validation step to verify index consistency.

---

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud