ci: release job on Node 22 so npm publish stops failing (v5.2.3)#16
Merged
Conversation
The release job installed npm@latest (needed for trusted-publishing, npm >=11.5.1) on Node 20, but npm 12.x requires Node >=22.22 — it failed with EBADENGINE and aborted npm publish + the GitHub Release for every v5.2.x tag (the container image built in a separate job, so Swarm deploys were unaffected, but the npm package and GitHub Releases went stale). Bump the release job to Node 22. Version bump to 5.2.3 cuts a release that validates the fix and finally publishes the accumulated 5.2.x fixes to npm.
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.
Why
The
releaseworkflow'snpm install -g npm@lateststep (needed for trusted publishing, which requires npm ≥ 11.5.1) ran on Node 20, but npm 12.x requires Node ≥ 22.22 →EBADENGINE, abortingnpm publishand the GitHub Release on everyv5.2.xtag. The container image builds in a separate job, so Swarm deploys were fine — but the npm package and GitHub Releases went stale (npm still at 5.1.0).Fix
Bump the release job's
setup-nodeto Node 22 sonpm@latestinstalls cleanly and provenance publishing works.Validation
Cutting 5.2.3 (no library-code change vs 5.2.2 — CI + version only) exercises the fixed workflow and finally publishes the accumulated 5.2.x fixes (OOM, stall, search-syntax) to npm. The Swarm stays on the functionally-identical 5.2.2 image; no redeploy needed.