meta: bump the next-js group with 2 updates #6592
Closed
Conversation
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
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps the next-js group with 2 updates: [next](https://github.com/vercel/next.js) and [turbo](https://github.com/vercel/turbo). Updates `next` from 14.1.3 to 14.1.4 - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.1.3...v14.1.4) Updates `turbo` from 1.12.5 to 1.13.0 - [Release notes](https://github.com/vercel/turbo/releases) - [Changelog](https://github.com/vercel/turbo/blob/main/release.md) - [Commits](vercel/turborepo@v1.12.5...v1.13.0) --- updated-dependencies: - dependency-name: next dependency-type: direct:production update-type: version-update:semver-patch dependency-group: next-js - dependency-name: turbo dependency-type: direct:development update-type: version-update:semver-minor dependency-group: next-js ... Signed-off-by: dependabot[bot] <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
github-actions
bot
removed
the
github_actions:pull-request
AugustinMauroy
approved these changes
Apr 1, 2024
aymen94
approved these changes
Apr 2, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to a conflict with the base branch
|
Superseded by #6610. |
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 the next-js group with 2 updates: next and turbo.
Updates
nextfrom 14.1.3 to 14.1.4Release notes
Sourced from next's releases.
Commits
f1fc357v14.1.4e6a117b(backport) Update React from 60a927d04 to 4b84f1161 (#63476)c227315update assertion due to stack trace change3aae252test: switch order of tests to avoid flakniess (#63482)4804982fix broken create-next-app tests (#63019)81114f3fix revalidation issue with route handlers (#63213)944a84censure mpa navigations to the same URL work after restoring from bfcache (#63...21e11f1Ensure PromiseLikeOfReactNode is not included in .d.ts files (#63185)531cdb5Fix metadata url cases should not append with trailing slash (#63050)a3707f5feat: adddeploymentIdconfig (#63198)Updates
turbofrom 1.12.5 to 1.13.0Release notes
Sourced from turbo's releases.
... (truncated)
Commits
f52f9ddpublish 1.13.0 to registryfc8a05bfeat: support apple git in scan diagnostic (#7740)ada6815docs: document new ui configuration options (#7803)2a7b6c6fix(ci): fix examples CI check (#7801)f4ad616Bug fix on kitchen-sink example (#7624)96baf61Support import.meta.env in eslint-plugin-turbo (#7781)bb464e3feat: add ability to control UI via cli arg (#7793)d61641brelease(turborepo): 1.13.0-canary.4 (#7794)07c60a4feat(pnpm): respect link-workspace-packages npmrc (#7791)25fa656Turbopack: Emit an issue on unknown module types instead of falling back to r...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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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 conditions