Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

meta: bump the next-js group with 2 updates #6690

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github May 1, 2024

Bumps the next-js group with 2 updates: next and turbo.

Updates next from 14.1.4 to 14.2.3

Release notes

Sourced from next's releases.

v14.2.3

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Fix: resolve mixed re-exports module as cjs (#64681)
  • fix: mixing namespace import and named import client components (#64809)
  • Fix mixed exports in server component with barrel optimization (#64894)
  • Fix next/image usage in mdx(#64875)
  • fix(fetch-cache): fix additional typo, add type & data validation (#64799)
  • prevent erroneous route interception during lazy fetch (#64692)
  • fix root page revalidation when redirecting in a server action (#64730)
  • fix: remove traceparent from cachekey should not remove traceparent from original object (#64727)
  • Clean-up fetch metrics tracking (#64746)

Credits

Huge thanks to @​huozhi, @​samcx, @​ztanner, @​Jeffrey-Zutt, and @​ijjk for helping!

v14.2.2

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

  • Fix Server Action error logs for unhandled POST requests (#64315)
  • Improve rendering performance (#64408)
  • Fix the method prop case in Server Actions transform (#64398)
  • fix(next-lint): update option --report-unused-disable-directives to --report-unused-disable-directives-severity (#64405)
  • tweak test for Azure (#64424)
  • router restore should take priority over pending actions (#64449)
  • Fix client boundary inheritance for barrel optimization (#64467)
  • improve turborepo caching (#64493)
  • feat: strip traceparent header from cachekey (#64499)
  • Fix more Turbopack build tests
  • Update lockfile for compatibility with turbo (#64360)
  • Fix typo in dynamic-rendering.ts (#64365)
  • Fix DynamicServerError not being thrown in fetch (#64511)
  • fix(next): Metadata.openGraph values not resolving basic values when type is set (#63620)
  • disable production chunking in dev (#64488)
  • Fix cjs client components tree-shaking (#64558)
  • fix refresh behavior for discarded actions (#64532)
  • fix: filter out middleware requests in logging (#64549)
  • Turbopack: Allow client components to be imported in app routes (#64520)
  • Fix ASL bundling for dynamic css (#64451)
  • add pathname normalizer for actions (#64592)
  • fix incorrect refresh request when basePath is set (#64589)
  • test: skip turbopack build test (#64356)
  • hotfix(turbopack): Update with patch for postcss.config.js path resolution on Windows (#64677)

... (truncated)

Commits
  • 2e7a96a v14.2.3
  • a230be4 Clean-up fetch metrics tracking (#64746)
  • 73c2d63 fix: remove traceparent from cachekey should not remove traceparent from orig...
  • dd44191 fix root page revalidation when redirecting in a server action (#64730)
  • 8b4c234 prevent erroneous route interception during lazy fetch (#64692)
  • d6a7ca0 fix(fetch-cache): fix additional typo, add type & data validation (#64799)
  • 4a6b511 Fix next/image usage in mdx (#64875)
  • 04cc13c Fix mixed exports in server component with barrel optimization (#64894)
  • 8d01d49 fix: mixing namespace import and named import client components (#64809)
  • de84e3a Fix: resolve mixed re-exports module as cjs (#64681)
  • Additional commits viewable in compare view

Updates turbo from 1.13.2 to 1.13.3

Release notes

Sourced from turbo's releases.

Turborepo v1.13.3-canary.3

What's Changed

Changelog

Full Changelog: vercel/turbo@v1.13.3-canary.2...v1.13.3-canary.3

Turborepo v1.13.3-canary.2

What's Changed

Docs

turbo-ignore

Changelog

New Contributors

Full Changelog: vercel/turbo@v1.13.3-canary.1...v1.13.3-canary.2

Turborepo v1.13.3-canary.1

What's Changed

Docs

create-turbo

eslint

@​turbo/telemetry

Examples

Changelog

... (truncated)

Commits
  • 3f46456 publish 1.13.3 to registry
  • 326b541 fix(telemetry): correctly parse alerted date (#8042)
  • 5e5f7d9 feat(turborepo): Process package change events asynchronously (#8036)
  • 09b266c chore: remove repetitive words (#8032)
  • db0eaf2 feat(Turborepo): support inputs for file hash watching (#7907)
  • 9783846 Remove can_be_in_same_chunk (#8029)
  • e63b1a8 chore: fix turborepo-repository MUSL release (#8028)
  • ef3b09b chore(ci): bump protoc version (#8025)
  • ab004db chore(ci): pin Github Actions runner that builds turborepo to macos-12 (#8024)
  • da53c14 feat(turborepo): Persistent Tasks in Watch Mode (#7922)
  • Additional commits viewable in compare view

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will 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 version will 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

@dependabot dependabot bot requested a review from a team as a code owner May 1, 2024 17:24
@dependabot dependabot bot added the github_actions:pull-request Trigger Pull Request Checks label May 1, 2024
Copy link

vercel bot commented May 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Updated (UTC)
nodejs-org ⬜️ Ignored (Inspect) Visit Preview May 3, 2024 5:07pm

@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label May 1, 2024
@AugustinMauroy AugustinMauroy added the github_actions:pull-request Trigger Pull Request Checks label May 1, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label May 1, 2024
@AugustinMauroy
Copy link
Contributor

I got an issue here. I'm not able to reproduce the failure on my machine 😅

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/next-js-4502381e04 branch 2 times, most recently from af5742f to 5d49822 Compare May 3, 2024 14:27
@bmuenzenmeyer bmuenzenmeyer added the github_actions:pull-request Trigger Pull Request Checks label May 3, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label May 3, 2024
@bmuenzenmeyer
Copy link
Collaborator

I got an issue here. I'm not able to reproduce the failure on my machine 😅

same

@AugustinMauroy
Copy link
Contributor

@dependabot rebase

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/next-js-4502381e04 branch from 5d49822 to a04dee3 Compare May 3, 2024 16:47
@AugustinMauroy AugustinMauroy added the github_actions:pull-request Trigger Pull Request Checks label May 3, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label May 3, 2024
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.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/turbo@v1.13.2...v1.13.3)

---
updated-dependencies:
- 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 dependabot bot force-pushed the dependabot/npm_and_yarn/next-js-4502381e04 branch from a04dee3 to 7570f70 Compare May 3, 2024 17:07
@AugustinMauroy AugustinMauroy added the github_actions:pull-request Trigger Pull Request Checks label May 3, 2024
@github-actions github-actions bot removed the github_actions:pull-request Trigger Pull Request Checks label May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants