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

fix(deps): update next.js to v14.2.23 #474

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 3, 2024

This PR contains the following updates:

Package Type Update Change OpenSSF
@next/bundle-analyzer (source) dependencies patch 14.2.13 -> 14.2.23 OpenSSF Scorecard
eslint-config-next (source) devDependencies patch 14.2.13 -> 14.2.23 OpenSSF Scorecard

Release Notes

vercel/next.js (@​next/bundle-analyzer)

v14.2.23

Compare Source

v14.2.22

Compare Source

v14.2.21

Compare Source

v14.2.20

Compare Source

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

Core Changes
Credits

Huge thanks to @​wyattjoh for helping!

v14.2.19

Compare Source

v14.2.18

Compare Source

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

Core Changes
Credits

Huge thanks to @​huozhi and @​ijjk for helping!

v14.2.17

Compare Source

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

Core Changes
  • Fix: revert the bad node binary handling (#​72356)
  • Ensure pages/500 handles cache-control as expected (#​72050) (#​72110)
  • fix unhandled runtime error from generateMetadata in parallel routes (#​72153)
Credits

Huge thanks to @​huozhi, @​ztanner, and @​ijjk for helping!

v14.2.16

Compare Source

v14.2.15

Compare Source

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

Core Changes
  • support breadcrumb style catch-all parallel routes #​65063
  • Provide non-dynamic segments to catch-all parallel routes #​65233
  • Fix client reference access causing metadata missing #​70732
  • feat(next/image): add support for decoding prop #​70298
  • feat(next/image): add images.localPatterns config #​70529
  • fix(next/image): handle undefined images.localPatterns config in images-manifest.json
  • fix: Do not omit alt on getImgProps return type, ImgProps #​70608
  • [i18n] Routing fix #​70761
Credits

Huge thanks to @​ztanner, @​agadzik, @​huozhi, @​styfle, @​icyJoseph and @​wyattjoh for helping!

v14.2.14

Compare Source

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

Core Changes
  • Fix: clone response in first handler to prevent race (#​70082) (#​70649)
  • Respect reexports from metadata API routes (#​70508) (#​70647)
  • Externalize node binary modules for app router (#​70646)
  • Fix revalidateTag() behaviour when invoked in server components (#​70446) (#​70642)
  • Fix prefetch bailout detection for nested loading segments (#​70618)
  • Add missing node modules to externals (#​70382)
  • Feature: next/image: add support for images.remotePatterns.search (#​70302)
Credits

Huge thanks to @​styfle, @​ztanner, @​ijjk, @​huozhi and @​wyattjoh for helping!

vercel/next.js (eslint-config-next)

v14.2.23

Compare Source

v14.2.22

Compare Source

v14.2.21

Compare Source

v14.2.20

Compare Source

v14.2.19

Compare Source

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

Core Changes
  • ensure worker exits bubble to parent process (#​73433)
  • Increase max cache tags to 128 (#​73125)
Misc Changes
  • Update max tag items limit in docs (#​73445)
Credits

Huge thanks to @​ztanner and @​ijjk for helping!

v14.2.18

Compare Source

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

Core Changes
Credits

Huge thanks to @​huozhi and @​ijjk for helping!

v14.2.17

Compare Source

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

Core Changes
  • Fix: revert the bad node binary handling (#​72356)
  • Ensure pages/500 handles cache-control as expected (#​72050) (#​72110)
  • fix unhandled runtime error from generateMetadata in parallel routes (#​72153)
Credits

Huge thanks to @​huozhi, @​ztanner, and @​ijjk for helping!

v14.2.16

Compare Source

v14.2.15

Compare Source

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

Core Changes
  • support breadcrumb style catch-all parallel routes #​65063
  • Provide non-dynamic segments to catch-all parallel routes #​65233
  • Fix client reference access causing metadata missing #​70732
  • feat(next/image): add support for decoding prop #​70298
  • feat(next/image): add images.localPatterns config #​70529
  • fix(next/image): handle undefined images.localPatterns config in images-manifest.json
  • fix: Do not omit alt on getImgProps return type, ImgProps #​70608
  • [i18n] Routing fix #​70761
Credits

Huge thanks to @​ztanner, @​agadzik, @​huozhi, @​styfle, @​icyJoseph and @​wyattjoh for helping!

v14.2.14

Compare Source

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

Core Changes
  • Fix: clone response in first handler to prevent race (#​70082) (#​70649)
  • Respect reexports from metadata API routes (#​70508) (#​70647)
  • Externalize node binary modules for app router (#​70646)
  • Fix revalidateTag() behaviour when invoked in server components (#​70446) (#​70642)
  • Fix prefetch bailout detection for nested loading segments (#​70618)
  • Add missing node modules to externals (#​70382)
  • Feature: next/image: add support for images.remotePatterns.search (#​70302)
Credits

Huge thanks to @​styfle, @​ztanner, @​ijjk, @​huozhi and @​wyattjoh for helping!


Configuration

📅 Schedule: Branch creation - "before 4am on Monday,before 4am on Thursday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot requested a review from JoeKarow as a code owner October 3, 2024 01:34
Copy link

vercel bot commented Oct 3, 2024

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

Name Status Preview Comments Updated (UTC)
transmascfutures ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 21, 2025 11:24pm

@renovate renovate bot added automerge Enable Kodiak auto-merge dependencies Change in project dependencies. labels Oct 3, 2024
Copy link

coderabbitai bot commented Oct 3, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary or <!-- #coderabbitai summary --> to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

socket-security bot commented Oct 3, 2024

Updated dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/@next/[email protected] 🔁 npm/@next/[email protected] None 0 3.38 kB vercel-release-bot
npm/[email protected] 🔁 npm/[email protected] Transitive: environment, eval, filesystem, shell +92 12.9 MB timer, timneutkens, vercel-release-bot

View full report↗︎

Copy link

relativeci bot commented Oct 3, 2024

#671 Bundle Size — 18.76MiB (~+0.01%).

392d24b(current) vs e0a1f6e dev#406(baseline)

Bundle metrics  Change 4 changes Regression 2 regressions
                 Current
#671
     Baseline
#406
Regression  Initial JS 1005.77KiB(~+0.01%) 1005.73KiB
Regression  Initial CSS 6.87KiB(+3.92%) 6.61KiB
Change  Cache Invalidation 2.34% 4.43%
No change  Chunks 20 20
No change  Assets 80 80
No change  Modules 792 792
No change  Duplicate Modules 103 103
Change  Duplicate Code 5.65%(-0.18%) 5.66%
No change  Packages 81 81
No change  Duplicate Packages 0 0
Bundle size by type  Change 3 changes Regression 2 regressions Improvement 1 improvement
                 Current
#671
     Baseline
#406
No change  IMG 17.47MiB 17.47MiB
Regression  JS 1.09MiB (~+0.01%) 1.09MiB
No change  Fonts 189.64KiB 189.64KiB
Regression  CSS 6.87KiB (+3.92%) 6.61KiB
Improvement  Other 4.06KiB (-0.12%) 4.07KiB

Bundle analysis reportBranch renovate/next.jsProject dashboard


Generated by RelativeCIDocumentationReport issue

@renovate renovate bot force-pushed the renovate/next.js branch from 72163a8 to 96a2e9d Compare October 8, 2024 21:10
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.14 fix(deps): update next.js Oct 8, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from 96a2e9d to 102e1db Compare October 9, 2024 00:34
@renovate renovate bot changed the title fix(deps): update next.js fix(deps): update next.js to v14.2.15 Oct 9, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from 102e1db to ea39f3c Compare October 23, 2024 03:07
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.15 fix(deps): update next.js to v14.2.16 Oct 23, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from ea39f3c to e25ea33 Compare November 6, 2024 04:29
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.16 fix(deps): update next.js to v14.2.17 Nov 6, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from e25ea33 to b725a95 Compare November 13, 2024 22:07
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.17 fix(deps): update next.js to v14.2.18 Nov 13, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from b725a95 to 675b9b4 Compare December 3, 2024 18:42
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.18 fix(deps): update next.js to v14.2.19 Dec 3, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from 675b9b4 to 18085b9 Compare December 4, 2024 23:25
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.19 fix(deps): update next.js to v14.2.20 Dec 4, 2024
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.20 fix(deps): update next.js to v14.2.21 Dec 19, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from 18085b9 to 8303063 Compare December 19, 2024 12:07
@renovate renovate bot force-pushed the renovate/next.js branch from 8303063 to 923b167 Compare December 26, 2024 18:24
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.21 fix(deps): update next.js to v14.2.22 Dec 26, 2024
@renovate renovate bot changed the title fix(deps): update next.js to v14.2.22 fix(deps): update next.js to v14.2.23 Jan 7, 2025
@renovate renovate bot force-pushed the renovate/next.js branch from 923b167 to 7e5e80f Compare January 7, 2025 20:18
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/next.js branch from 7e5e80f to 392d24b Compare January 21, 2025 23:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge Enable Kodiak auto-merge dependencies Change in project dependencies.
Development

Successfully merging this pull request may close these issues.

0 participants