chore(deps): bump the npm_and_yarn group across 1 directory with 2 updates - #101
Merged
Merged
Conversation
…dates Bumps the npm_and_yarn group with 2 updates in the / directory: [next](https://github.com/vercel/next.js) and [sharp](https://github.com/lovell/sharp). Updates `next` from 16.3.1 to 16.3.3 - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.3.1...v16.3.3) Updates `sharp` from 0.35.3 to 0.35.4 - [Release notes](https://github.com/lovell/sharp/releases) - [Commits](lovell/sharp@v0.35.3...v0.35.4) --- updated-dependencies: - dependency-name: next dependency-version: 16.3.3 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: sharp dependency-version: 0.35.4 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
acamarata
approved these changes
Sep 11, 2026
acamarata
left a comment
acamarata
left a comment
Collaborator
There was a problem hiding this comment.
Third-party dependency bump. All 34 checks green, none failing, none pending. No nSelf package version changed.
acamarata
deleted the
dependabot/npm_and_yarn/npm_and_yarn-5248377724
branch
September 11, 2026 08:01
acamarata
added a commit
that referenced
this pull request
Sep 11, 2026
pnpm audit found 2 critical (GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4, both in next <16.3.3) and 6 high/9 moderate advisories, failing the Dependency Audit workflow on main and blocking Dependabot's grouped security-update PRs (security_update_not_possible for 8 deps whose fix required a workspace-root override, not a direct bump). Rebased onto main after #101 (Dependabot's own auto-merged next/sharp patch) landed mid-fix; this PR covers the remaining 8+ transitive advisories - add/tighten pnpm.overrides for transitive deps, each scoped to the existing major to avoid surprise jumps: @babel/core, @humanfs/node, @opentelemetry/core, decode-uri-component, linkify-it, js-yaml (v3 and v4 branches scoped separately), uuid - raise existing fast-xml-parser and protobufjs override floors to their patched versions - add a path-scoped override for webpack-bundle-analyzer>ws: the existing blanket "ws@>=8.0.0" override was not being honored for this transitive edge, leaving ws@8.20.0 resolved and vulnerable despite the override already being present in package.json Not fixed: stream-json (GHSA-528h-pc64-c93x, moderate, path minio>stream-json). minio@8.0.7 (latest) hard-depends on stream-json@^1.8.0 and requires 'stream-json/jsonl/Parser.js', a file path removed in the patched 3.5.0+ release. Overriding to 3.x broke the production build (verified locally and on this PR's CI). No fix is possible without minio releasing a stream-json 3.x- compatible version or replacing minio; left as-is pending an owner decision. Verified via `pnpm audit --json` against the regenerated lockfile: critical/high/moderate/low now 0/0/1/0 (was 2/6/9/1); the 1 remaining moderate is the stream-json finding above.
acamarata
added a commit
that referenced
this pull request
Sep 11, 2026
…ps (#102) pnpm audit found 2 critical (GHSA-p293-qw3h-jr36, GHSA-2xp9-vwfh-vxw4, both in next <16.3.3) and 6 high/9 moderate advisories, failing the Dependency Audit workflow on main and blocking Dependabot's grouped security-update PRs (security_update_not_possible for 8 deps whose fix required a workspace-root override, not a direct bump). Rebased onto main after #101 (Dependabot's own auto-merged next/sharp patch) landed mid-fix; this PR covers the remaining 8+ transitive advisories - add/tighten pnpm.overrides for transitive deps, each scoped to the existing major to avoid surprise jumps: @babel/core, @humanfs/node, @opentelemetry/core, decode-uri-component, linkify-it, js-yaml (v3 and v4 branches scoped separately), uuid - raise existing fast-xml-parser and protobufjs override floors to their patched versions - add a path-scoped override for webpack-bundle-analyzer>ws: the existing blanket "ws@>=8.0.0" override was not being honored for this transitive edge, leaving ws@8.20.0 resolved and vulnerable despite the override already being present in package.json Not fixed: stream-json (GHSA-528h-pc64-c93x, moderate, path minio>stream-json). minio@8.0.7 (latest) hard-depends on stream-json@^1.8.0 and requires 'stream-json/jsonl/Parser.js', a file path removed in the patched 3.5.0+ release. Overriding to 3.x broke the production build (verified locally and on this PR's CI). No fix is possible without minio releasing a stream-json 3.x- compatible version or replacing minio; left as-is pending an owner decision. Verified via `pnpm audit --json` against the regenerated lockfile: critical/high/moderate/low now 0/0/1/0 (was 2/6/9/1); the 1 remaining moderate is the stream-json finding above.
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.
Bumps the npm_and_yarn group with 2 updates in the / directory: next and sharp.
Updates
nextfrom 16.3.1 to 16.3.3Release notes
Sourced from next's releases.
Commits
a9a1cb7v16.3.3968b9fc[16.3.x] Fix ISR misses with backslashes in segments when deployed on Windows3a15b4a[16.3.x] [next/image]: disable avif image optimization7378b51Backport/docs fixes 16.3 (#97649)528c1cd[16.3.x] Stop generating error codes (#97780)d0ac882v16.3.281deb92[16.3.x] Authenticate Turborepo remote caching with OIDC instead of a static ...cd714d9[16.3.x] Fix Turbopack worker chunk loading with asset prefix (#97419)5ac2327[16.3] Turbopack: retain conditions when replacing resolve request keys (#97453)0ccb3e7[16.3] Turbopack: don't trace embedded WASM loader helpers (#97353) (#97463)Updates
sharpfrom 0.35.3 to 0.35.4Release notes
Sourced from sharp's releases.
Commits
7f1a0a2Release v0.35.4f927818Upgrade to sharp-libvips v1.3.3e802092Prerelease v0.35.4-rc.0e13eb2fCI: Fix wasm32 build (#4589)a82a0b3Upgrade to libvips v8.18.68044fe4Bound resize dimensions to coordinate limit147f859Docs: changelog entries for #4578 #4584ee5bfb8Tests: use yauzl directly rather than via extract-zip wrapper7a77889Bump uraimo/run-on-arch-action from 3.1.0 to 3.2.0 (#4588)ea5bef2Improve support for input Streams finishing before output is requested (#4584)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.