Repository navigation
chore(deps): bump shell-quote and sharp in root npm lockfile - #5361
Merged
Merged
Conversation
Contributor
Author
|
Merging over a known, pre-existing
Why this is pre-existing:
Every other check that ran on this PR passed, including the job(s) that cover the changed lockfile. |
This was referenced Oct 8, 2026
Merged
This was referenced Oct 16, 2026
Merged
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.
Routine dependency maintenance for the root npm workspace lockfile. It follows up on #5311 for two advisories published after that PR was opened.
Closes Dependabot alerts #1848 #1849
@img/sharp-*platform packages, libvips 1.3.3 → 1.3.4)Both are in-range updates under the existing overrides (
"shell-quote": ">=1.9.0","sharp": ">=0.35.4"), sopackage.jsonis unchanged. The lockfile was regenerated with npm 11 (npx npm@11 update sharp shell-quote --package-lock-only), because npm 10.9.x mishandles overrides in workspaces. npm 11 also recordslibcon the new sharp platform entries.Verification (npm 10.9.2
npm cifrom the committed lockfile)sharp.versionsreports 0.35.5 / vips 8.18.7parse/quoteround-tripnpm run build: typescript client, hindsight-control-plane (Next.js), hindsight-all-npm, agent-sdk, and hindsight-docs (docusaurus build) all pass. The control-plane and docs CSS output is byte-identical to beforenpm test: control-plane 289/289, all-npm, agent-sdk all pass