🚨 [security] Update all of nextjs 15.4.3 → 15.4.7 (patch)#336
Closed
depfu[bot] wants to merge 1 commit intomainfrom
Closed
🚨 [security] Update all of nextjs 15.4.3 → 15.4.7 (patch)#336depfu[bot] wants to merge 1 commit intomainfrom
depfu[bot] wants to merge 1 commit intomainfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
|
Closed in favor of #339. |
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-config-next (14.2.30 → 15.4.7)
Sorry, we couldn't find anything useful about this release.
✳️ next (15.4.3 → 15.4.7) · Repo
Security Advisories 🚨
🚨 Next.js Content Injection Vulnerability for Image Optimization
🚨 Next.js Affected by Cache Key Confusion for Image Optimization API Routes
🚨 Next.js Improper Middleware Redirect Handling Leads to SSRF
Release Notes
15.4.7
15.4.6
15.4.5
15.4.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 20 commits:
v15.4.7fix router handling when setting a location response header (#82588)v15.4.6Backport "fix: add `?dpl` to fonts in `/_next/static/media` (#82384)" (#82421)Backport "[Pages] fix: `_error` page's `req.url` can be overwritten t… (#82377)v15.4.5Disable test new tests jobs[backport]: fix(next/image): improve and simplify detect-content-type (#82118) (#82174)[backport]: fix(next/image): fix image-optimizer.ts headers (#82114) (#82175)Backport: Turbopack: update mimalloc (#81993) (#82166)[backport] Ensure setAssetPrefix updates config instance (#82165)[Backport] Revert "Fix tracing of server actions imported by client components (#78968) (#82167)[backport] Fix i18n fallback: false collision (#82158)Fix API stripping JSON incorrectly (#82062)v15.4.4[backport] Fix dynamicParams false layout case in dev (#82026)Turbopack: fix scope hoisting variable renaming bug (#81640)Upgrade to swc v33 (#81750)Turbopack: Use workaround for rustc miscompilation bug on macos intelRevert "[metadata] use https protocol for schema urls" (#81934)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands