meta: bump the next-js group across 1 directory with 4 updates #6742
Conversation
This file contains 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}
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
github-actions
bot
removed
the
github_actions:pull-request
|
Something seems broken now with Shiki when using latest Next.js |
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-js-1d0d9cdef4
branch
4 times, most recently
from
91276fa
to
ae73348
Compare
|
@ovflowd we can ignore nextjs for now and merge for other package ? |
Bumps the next-js group with 4 updates in the / directory: [@vercel/analytics](https://github.com/vercel/analytics/tree/HEAD/packages/web), [@vercel/speed-insights](https://github.com/vercel/speed-insights/tree/HEAD/packages/web), [next](https://github.com/vercel/next.js) and [turbo](https://github.com/vercel/turbo). Updates `@vercel/analytics` from 1.2.2 to 1.3.1 - [Release notes](https://github.com/vercel/analytics/releases) - [Commits](https://github.com/vercel/analytics/commits/1.3.1/packages/web) Updates `@vercel/speed-insights` from 1.0.10 to 1.0.11 - [Release notes](https://github.com/vercel/speed-insights/releases) - [Commits](https://github.com/vercel/speed-insights/commits/1.0.11/packages/web) Updates `next` from 14.1.4 to 14.2.3 - [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.4...v14.2.3) Updates `turbo` from 1.13.2 to 1.13.3 - [Release notes](https://github.com/vercel/turbo/releases) - [Changelog](https://github.com/vercel/turbo/blob/main/release.md) - [Commits](vercel/turborepo@v1.13.2...v1.13.3) --- updated-dependencies: - dependency-name: "@vercel/analytics" dependency-type: direct:production update-type: version-update:semver-minor dependency-group: next-js - dependency-name: "@vercel/speed-insights" dependency-type: direct:production update-type: version-update:semver-patch dependency-group: next-js - dependency-name: next dependency-type: direct:production update-type: version-update:semver-minor dependency-group: next-js - dependency-name: turbo dependency-type: direct:development update-type: version-update:semver-patch dependency-group: next-js ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/next-js-1d0d9cdef4
branch
from
ae73348
to
e3ed25f
Compare
|
I had a stab at this today but didn't make a lot of progress. Site runs fine on latest nextjs without the turbo flag. With turbo something CSS related is definitely failing |
|
Looks like these dependencies are no longer updatable, so this is no longer needed. |
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 4 updates in the / directory: @vercel/analytics, @vercel/speed-insights, next and turbo.
Updates
@vercel/analyticsfrom 1.2.2 to 1.3.1Release notes
Sourced from
@vercel/analytics's releases.Commits
cc5a474fix: nextjs parallel routes with catchall isn't supported (#141)74942cd[web] Include flags in custom events (#140)Updates
@vercel/speed-insightsfrom 1.0.10 to 1.0.11Release notes
Sourced from
@vercel/speed-insights's releases.Commits
fe76ed0fix(#68): postinstall is failing with no error68d3424fix: nextjs parallel routes with catchall isn't supported (#69)Updates
nextfrom 14.1.4 to 14.2.3Release notes
Sourced from next's releases.
... (truncated)
Commits
2e7a96av14.2.3a230be4Clean-up fetch metrics tracking (#64746)73c2d63fix: remove traceparent from cachekey should not remove traceparent from orig...dd44191fix root page revalidation when redirecting in a server action (#64730)8b4c234prevent erroneous route interception during lazy fetch (#64692)d6a7ca0fix(fetch-cache): fix additional typo, add type & data validation (#64799)4a6b511Fix next/image usage in mdx (#64875)04cc13cFix mixed exports in server component with barrel optimization (#64894)8d01d49fix: mixing namespace import and named import client components (#64809)de84e3aFix: resolve mixed re-exports module as cjs (#64681)Updates
turbofrom 1.13.2 to 1.13.3Release notes
Sourced from turbo's releases.
... (truncated)
Commits
3f46456publish 1.13.3 to registry326b541fix(telemetry): correctly parse alerted date (#8042)5e5f7d9feat(turborepo): Process package change events asynchronously (#8036)09b266cchore: remove repetitive words (#8032)db0eaf2feat(Turborepo): support inputs for file hash watching (#7907)9783846Removecan_be_in_same_chunk(#8029)e63b1a8chore: fix turborepo-repository MUSL release (#8028)ef3b09bchore(ci): bump protoc version (#8025)ab004dbchore(ci): pin Github Actions runner that builds turborepo to macos-12 (#8024)da53c14feat(turborepo): Persistent Tasks in Watch Mode (#7922)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