Repository navigation
build: regenerate the website lockfile with npm 10 - #826
Merged
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
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.
Why
The Website workflow's
npm cifails onmain: the lockfile was written by npm 11, and the npm 10 bundled with Node 22 on the runner expects extra optional@emnapientries, so the site never built or deployed.Changes
website/package-lock.jsonwith npm 10.9.9.Verification
npm cisucceeds with both npm 10.9.9 and npm 11.6.2 under Node 22.npm run buildandscripts/check_links.py: 107 pages, 0 broken links.