Skip to content

fix(ci): keep publish compatible with pinned Node - #19

Merged
maxigimenez merged 1 commit into
mainfrom
fix/publish-node-compatibility
Sep 3, 2026
Merged

maxigimenez merged 1 commit into
mainfrom
fix/publish-node-compatibility

Conversation

@maxigimenez

Copy link
Copy Markdown
Owner

Cause

The v0.2.0 publish job passed the complete package check, then failed before npm publish because npm@latest resolved to npm 12.0.2. That npm release requires Node 24.15.0+, while this repository intentionally pins Node 24.13.1.

Fix

  • use the npm 11.8.0 bundled with Node 24.13.1, which supports npm trusted publishing
  • add workflow_dispatch so the existing release can be retried without deleting or moving v0.2.0

Verification

  • pnpm check passed
  • 25 tests passed
  • all 22 package exports verified
  • Storybook production build passed
  • npm registry still reports 0.1.0, confirming 0.2.0 was not partially published

@maxigimenez
maxigimenez merged commit 4802a13 into main Sep 3, 2026
1 check 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