Fix npm trusted publishing runtime - #60
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Keep package build and regression tests on the minimum supported Node 20.11.0, then switch to Node 24 for the final npm trusted-publishing step.
Why
The v1.3.4 tag build and package tests passed, but Node 20.11 ships an npm version without GitHub OIDC trusted-publishing support. npm fell back to token-style publication and the registry returned 404.
Release recovery
After merge, dispatch the CI workflow from main with
dry_run=false. The v1.3.4 source tag remains unchanged because this only alters release orchestration; the package source and tarball remain the tested merge commit.