Update all of nextjs 14.1.3 → 14.1.4 (patch) #105
Merged
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.
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?
✳️ @next/eslint-plugin-next (14.1.3 → 14.1.4)
Sorry, we couldn't find anything useful about this release.
✳️ eslint-config-next (14.1.3 → 14.1.4)
Sorry, we couldn't find anything useful about this release.
✳️ next (14.1.3 → 14.1.4) · Repo
Release Notes
14.1.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
v14.1.4
(backport) Update React from 60a927d04 to 4b84f1161 (#63476)
update assertion due to stack trace change
test: switch order of tests to avoid flakniess (#63482)
fix broken create-next-app tests (#63019)
fix revalidation issue with route handlers (#63213)
ensure mpa navigations to the same URL work after restoring from bfcache (#63155)
Ensure PromiseLikeOfReactNode is not included in .d.ts files (#63185)
Fix metadata url cases should not append with trailing slash (#63050)
feat: add `deploymentId` config (#63198)
fix: bump `@vercel/nft@0.26.3` (#61538)
fix `x-forwarded-port` header (#63303)
fix: x-forwarded-port header is 'undefined' when no port in url (#60484)
Release Notes
14.1.4
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 13 commits:
v14.1.4
(backport) Update React from 60a927d04 to 4b84f1161 (#63476)
update assertion due to stack trace change
test: switch order of tests to avoid flakniess (#63482)
fix broken create-next-app tests (#63019)
fix revalidation issue with route handlers (#63213)
ensure mpa navigations to the same URL work after restoring from bfcache (#63155)
Ensure PromiseLikeOfReactNode is not included in .d.ts files (#63185)
Fix metadata url cases should not append with trailing slash (#63050)
feat: add `deploymentId` config (#63198)
fix: bump `@vercel/nft@0.26.3` (#61538)
fix `x-forwarded-port` header (#63303)
fix: x-forwarded-port header is 'undefined' when no port in url (#60484)
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