Repository navigation
deps: bump next from 16.3.8 to 16.4.2 - #17969
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [next](https://github.com/vercel/next.js) from 16.3.8 to 16.4.2. - [Release notes](https://github.com/vercel/next.js/releases) - [Commits](vercel/next.js@v16.3.8...v16.4.2) --- updated-dependencies: - dependency-name: next dependency-version: 16.4.2 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
CI Coverage Report
Coverage artifact was not available for this run. |
diegosouzapw
added a commit
that referenced
this pull request
Oct 24, 2026
Dependabot alerts #327 (high), #328 and #333 (critical) flag next >= 16.0.0, <= 16.4.0. Same version and lockfile delta as the Dependabot PR #17969 (next + @next/env + the @next/swc-* binaries 16.3.8 -> 16.4.2), whose Build, E2E 1-9/9, Electron package smoke and Ecosystem jobs passed with it. Landing it next to the dompurify bump clears all three critical npm audit findings on the base (dompurify, monaco-editor via dompurify, next), which the Lint job's `npm audit --audit-level=critical` blocks on; on separate PRs each one still carries the other's critical finding.
Contributor
Author
|
Superseded by #18092. |
diegosouzapw
added a commit
that referenced
this pull request
Oct 25, 2026
…n's toml (#18067) Fixes Dependabot alerts #325-#333: dompurify 3.4.16 -> 3.4.17 (dependency + monaco-editor override), ip-address 10.7.2 -> 10.7.4 (override), next 16.3.8 -> 16.4.2 (exact pin, same delta as #17969), and toml 4.3.0 -> 5.0.1 in @omniroute/opencode-plugin (override, approved major). Clears every critical npm audit finding on the base (Lint audit step) and brings vuln-ratchet from 29 to 22 (baseline 27).
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.
Bumps next from 16.3.8 to 16.4.2.
Release notes
Sourced from next's releases.
... (truncated)
Commits
2864b17v16.4.2a42cb59Revert "[lts-active] Keep requests through middleware in a single OpenTelemet...f0760ec[lts-active] Backport additional documentation fixes since v16.4.0 (#100262)845007a[lts-active] Fix Turbopack lazy dynamic-import chunk-list collisions (#100211)6a79d8a[lts-active] Backport docs fixes since v16.4.0 (#100246)a75a782[lts-active] Keep requests through middleware in a single OpenTelemetry trace...8ad8524[lts-active] Turbopack: Ignore realpath errors during module resolution, matc...29d030e[lts-active] [turbopack] Fix two GC paths that leave half-torn-down dependenc...3e50b82[lts-active] fix(next-code-frame): snap visible window to char boundaries (#1...9458fb9[lts-active] Turbopack: backport Pages Router dev module graph chaining (#988...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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.