fix(ci): pin Pages CI container to node:24.18.0#492
Merged
Conversation
The rolling `node:24` tag recently picked up a newer npm version whose `npm ci` rejects the existing lockfileVersion-3 lockfile. Pin to 24.18.0 (same version used by translation-sync.yml) to restore deterministic builds.
Contributor
|
✅ OpenCodeReview: No comments generated. Looks good to me. |
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
2 participants
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
pages-ci.ymlcontainer image from the rollingnode:24tag tonode:24.18.0npm ciwith the existing lockfileVersion-3 lockfile, breaking all PRs that touchpages/**(e.g. feat(llm): add iFlytek Spark as a built-in provider #485, perf(pages): enable webpack code splitting and lazy-load heavy dependencies #457)node:24.18.0is the same version already used bytranslation-sync.ymland is known to workContext
The
pages-ci.ymlworkflow was introduced in #442 withimage: node:24. At the time, the rolling tag pointed to a compatible npm version. Docker Hub has since updated the tag, causingnpm cito fail with a lockfile incompatibility error.