Repository navigation
Conversation
Runs `npm ci` weekly against the MDN repos that have dependencies with install scripts, using npm@latest instead of the npm bundled with Node.js. `--strict-allow-scripts` turns an incomplete `allowScripts` allowlist into a hard failure, so a dependency bump that adds an install script surfaces here rather than as a missing binary in a release job. Can be removed once all MDN repos run npm 12.
7 of 8 tasks
Contributor
Author
|
Closing as obsolete; we're setting |
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.
Description
Add
npm-latest-canary.yml, a weekly job that runsnpm ci --strict-allow-scriptsundernpm@latestagainst the 17 MDN repos affected by the npm 12 install-script changes.Motivation
Surface npm forward-compatibility regressions early. A Dependabot bump that adds a dependency with a new install script leaves that repo's
allowScriptsallowlist incomplete, and plainnpm cistill exits 0, so it would otherwise only show up as a missing binary in a build or release job.Additional details
--strict-allow-scriptsturns an uncovered install script into a hardESTRICTALLOWSCRIPTSfailure. Repos settingstrict-allow-scripts=truein their own.npmrcget that for free; the flag covers the rest..nvmrcwhen present and Node.js 24 otherwise, then installsnpm@lateston top: the point is to test npm, not Node.js.Related issues and pull requests
Part of mdn/fred#1868.