ci: add setup-node@v4 with Node 22 before npm ci in release workflow#81
Merged
zhukaihan merged 2 commits intocodex/release-lockfilesfrom Mar 20, 2026
Merged
ci: add setup-node@v4 with Node 22 before npm ci in release workflow#81zhukaihan merged 2 commits intocodex/release-lockfilesfrom
zhukaihan merged 2 commits intocodex/release-lockfilesfrom
Conversation
Co-authored-by: zhukaihan <7332407+zhukaihan@users.noreply.github.com> Agent-Logs-Url: https://github.com/amplitude/experiment-ruby-server/sessions/9cea838f-75a4-4b8b-98d8-1e0f6017660c
Copilot
AI
changed the title
[WIP] [WIP] Address feedback: Use Node 22 for NPM dependency setup
ci: add setup-node@v4 with Node 22 before npm ci in release workflow
Mar 20, 2026
zhukaihan
approved these changes
Mar 20, 2026
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
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.
The release workflow was running
npm ciwithout a pinned Node/npm version, risking failures when the runner image changes — particularly sincepackage-lock.jsonuseslockfileVersion: 3(requires npm v9+).Changes
actions/setup-node@v4step withnode-version: 22andcache: 'npm'in.github/workflows/release.yml, placed before bothnpm ciinvocationsSummary
Pins Node 22 in the release workflow to ensure a compatible npm version is always available for the committed lockfile.
Checklist
📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.