chore(supply-chain): bump axios, immutable and nanoid past new advisories - #126
Open
atepem wants to merge 1 commit into
Open
chore(supply-chain): bump axios, immutable and nanoid past new advisories#126atepem wants to merge 1 commit into
atepem wants to merge 1 commit into
Conversation
…ries `main` has been red since 2026-09-02: three high-severity advisories published against the production tree are not allowlisted, so every `Dependency audit` matrix entry fails — root and all eleven subgraphs. axios >=1.15.2 <1.18.0 -> 1.18.0 (1153178, GHSA-gcfj-64vw-6mp9) immutable >=5.0.0-beta.1 <5.1.8 -> 5.1.8 (1164790, GHSA-xvcm-6775-5m9r) nanoid >=4.0.0 <5.1.11 -> 5.1.11 (1153188, GHSA-xwg4-73v4-xw9w) All three have patched versions, so these are resolution bumps rather than allowlist entries. Pinned to the minimal patched version of each (not latest) to keep the change surface small: axios is on 1.20.0 and nanoid on 6.0.1 upstream, both beyond what the advisories require. The existing `axios: 1.17.0` pin was correct when set and was overtaken by 1153178. Resolutions are added to all twelve package.json files, per the convention that they converge across the repo, and every lockfile is regenerated. The diff touches only these three packages. Verified by running scripts/audit.mjs in each of the twelve CI matrix paths: all pass, no unlisted high/critical. Not addressed here: 59 allowlist entries have review dates that expired on 2026-08-06. Those emit warnings only and do not fail the build, so refreshing them is left to a separate pass. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
mainhas been red since 2 Sept. Three high-severity advisories published against the production tree are not allowlisted, so everyDependency auditmatrix entry fails — root and all eleven subgraphs. This unblocksmain, and with it #124 and #125.The three advisories
axiosimmutablenanoidAll three have patched versions, so these are resolution bumps rather than allowlist entries.
Pinned to the minimal patched version of each rather than latest, to keep the change surface small for a security fix —
axiosis on 1.20.0 upstream andnanoidon 6.0.1 (a major), both further than the advisories require. Happy to take the newer ones instead if you'd prefer fewer future bumps.The existing
axios: 1.17.0pin was correct when it was set; advisory 1153178 overtook it.Scope
Resolutions added to all twelve
package.jsonfiles, per the convention that they converge across the repo, and every lockfile regenerated. The diff touches only these three packages — verified by extracting every changed lockfile entry key.Verification
Ran
scripts/audit.mjsin each of the twelve CI matrix paths. All pass:Two notes for review
Generated on Node 22, not 24. Root
yarn installandyarn audit:prodboth refuse to run below theengines: ">=24.0.0"gate, so I used--ignore-enginesfor the install and invokedscripts/audit.mjsdirectly. This is safe for yarn 1.x — its lockfiles are resolution-only, with none of the platform-specific entries npm's have — and the resulting diff confirms it. CI on Node 24 is still the authoritative check; worth a glance at the lockfile diff before merging.59 expired allowlist entries, deliberately not touched here. Their review dates lapsed on 2026-08-06. They emit
::warning::only and do not fail the build (scripts/audit.mjsexits 1 solely for unlisted high/critical), so refreshing or retiring them is a separate pass with its own judgement calls. Flagging it because the log is noisy with them and it's easy to mistake for the cause.🤖 Generated with Claude Code