build(deps): bump nanoid to 3.3.18 in /docs (#425) - #430
Merged
Conversation
Dependabot opened #425 for this against `master`, which on this repo is a release pin that only ever fast-forwards from `dev` -- merging there would make master diverge and the next release FF would stop being a fast-forward. Security PRs ignore the configured target branch, so this lands on dev by hand instead and #425 is closed as superseded. dev was already at 3.3.16, ahead of the 3.3.11 the PR bumped from. Edited to the three lockfile lines rather than run `npm install nanoid@3.3.18`, which also adds nanoid to package.json as a direct dependency (it is transitive) and strips the `libc` platform metadata from four optional entries. `npm ci` accepts the result and the Astro build is unchanged at 31 pages.
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
1 participant
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.
Dependabot opened #425 for this against
master. Security PRs ignore the configured target branch, and master here is a release pin that only ever fast-forwards fromdev— merging there would make master diverge and the next release FF would stop being a fast-forward. So this lands on dev instead and #425 is closed as superseded. dev was already at 3.3.16, ahead of the 3.3.11 the PR bumped from.Closes #425.
AI-assisted detail
Hand-edited to the three lockfile lines rather than run
npm install nanoid@3.3.18, which also addsnanoidtodocs/package.jsonas a direct dependency (it is transitive, pulled in via postcss) and strips thelibcplatform metadata from four optional entries — churn unrelated to the advisory, and thelibcfields matter for musl-vs-glibc variant selection.npm update nanoid --package-lock-onlydid the same stripping.Verified:
npm ciaccepts the edited lockfile and resolves nanoid 3.3.18, andnpm run buildis unchanged at 31 pages.Not included:
npm auditalso reports js-yaml high severity (4.0.0–4.3.0, fix available), which is a separate advisory and not what #425 was about.