Skip to content

Conversation

@JanCizmar
Copy link
Contributor

@JanCizmar JanCizmar commented Feb 11, 2026

Summary

The release pipeline was broken because the NPM_TOKEN expired — npm classic tokens have been deprecated and capped to 90-day expiry.

This migrates to OIDC-based Trusted Publishers:

  • Upgrade lerna from 8.x to 9.x (OIDC support requires lerna >= 9.0.0)
  • Use Node 24 in release workflow (npm >= 11.5.1 required for OIDC, ships with Node 24)

Test plan

  • Prerelease pipeline published successfully with this change

Summary by CodeRabbit

  • Chores
    • Updated Node.js version from 22 to 24 in CI workflow for improved performance and latest runtime features.
    • Upgraded lerna development dependency to latest version for enhanced monorepo tooling support.

npm Trusted Publishers OIDC requires npm >= 11.5.1 (ships with Node
24) and lerna >= 9.0.0 for OIDC support.
@coderabbitai
Copy link

coderabbitai bot commented Feb 11, 2026

Walkthrough

Node.js runtime version bumped from 22 to 24 in CI workflow, and lerna DevDependency upgraded from ^8.1.9 to ^9.0.4 in package.json. No functional or control-flow changes.

Changes

Cohort / File(s) Summary
CI Configuration
.github/workflows/release.yml
Node.js version updated from 22 to 24 in the Setup node step.
Development Dependencies
package.json
Lerna DevDependency upgraded from ^8.1.9 to ^9.0.4.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Hop skip and bump, the versions dance high,
Node twenty-four reaches toward the sky,
Lerna leaps forth in its nine-dot-oh grace,
Configuration flows with a swift, springy pace! 🚀

🚥 Pre-merge checks | ✅ 3
✅ 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 summarizes the main changes: upgrading to Node 24 and lerna 9 for npm Trusted Publishers support, which aligns with the actual file modifications and PR objectives.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch jancizmar/fix-release-node24

No actionable comments were generated in the recent review. 🎉

Tip

Issue Planner is now in beta. Read the docs and try it out! Share your feedback on Discord.


Comment @coderabbitai help to get the list of available commands and usage tips.

@JanCizmar JanCizmar merged commit 11e843d into main Feb 11, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant