Pin npm version to 11.6.2 #6455
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
govuk-design-system-ci
had a problem deploying
to
govuk-frontend-pr-6455
📋 StatsNo changes to any distributed file sizes! Action run for a311376 |
govuk-design-system-ci
had a problem deploying
to
govuk-frontend-pr-6455
querkmachine
force-pushed
the
npm-version-test
branch
from
88a12b7 to
a311376
Compare
govuk-design-system-ci
temporarily deployed
to
govuk-frontend-pr-6455
romaricpascal
approved these changes
Nov 21, 2025
Member
romaricpascal
left a comment
romaricpascal
left a comment
There was a problem hiding this comment.
Cheers for fixing this 🙌🏻
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.
npm 11.6.3 released on the evening of the 19th November. It seems to contain a bug that causes
npm cito fail ifoverridesare defined: npm/cli#8757This is causing our CI builds to fail, as our current package files specify that any version of 11.6.x is acceptable and tools are automatically using the latest version.
The interim solution seems to be to pin our npm version to 11.6.2 until a fix is available.
Work on that fix appears to be taking place here: npm/cli#8760