fix: bump Auto Release workflow to Node 22 - #20
Merged
Merged
Conversation
Merging PR #4 triggered Auto Release (its squash-merge commit starts with "feat:"), which failed at "Upgrade npm for OIDC": npm@latest now requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, and the workflow pins Node 20. No broken publish happened (it failed before the publish step, version stayed 3.0.3), but release automation was broken for any future feat/fix merge until this lands. Bumped to Node 22, which the CI test matrix in ci.yml already exercises.
✅ Deploy Preview for thunderous-starship-f6b99a canceled.
|
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.
Summary
Merging #4 triggered Auto Release (squash-merge commit started with
feat:), which failed at the "Upgrade npm for OIDC" step:npm install -g npm@latestnow requires Node^22.22.2 || ^24.15.0 || >=26.0.0, and the workflow pins Node 20. No broken publish happened — it failed before the publish step, npm still shows3.0.3— but release automation is broken for any futurefeat:/fix:merge until this lands.Bumped
NODE_VERSIONto22, whichci.yml's own test matrix already exercises.Test plan
🤖 Generated with Claude Code