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(web): update next.js to v14.2.23 #1435

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 Nov 6, 2024

This PR contains the following updates:

Package Type Update Change OpenSSF
@next/bundle-analyzer (source) devDependencies patch 14.2.16 -> 14.2.23 OpenSSF Scorecard
@next/bundle-analyzer (source) dependencies patch 14.2.16 -> 14.2.23 OpenSSF Scorecard
@next/eslint-plugin-next (source) devDependencies patch 14.2.16 -> 14.2.23 OpenSSF Scorecard
@next/third-parties (source) peerDependencies patch 14.2.16 -> 14.2.23 OpenSSF Scorecard
@next/third-parties (source) devDependencies patch 14.2.16 -> 14.2.23 OpenSSF Scorecard
@next/third-parties (source) dependencies patch 14.2.16 -> 14.2.23 OpenSSF Scorecard
eslint-config-next (source) devDependencies patch 14.2.16 -> 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!

vercel/next.js (@​next/eslint-plugin-next)

v14.2.23

Compare Source

v14.2.22

Compare Source

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

Core Changes
  • Retry manifest file loading only in dev mode: #​73900
  • Ensure workers are cleaned up: #​71564
  • Use shared worker for lint & typecheck steps: #​74154
Credits

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

v14.2.21

Compare Source

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

Core Changes
Misc Changes
Credits

Huge thanks to @​unstubbable, @​ztanner, and @​styfle for helping!

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!

vercel/next.js (@​next/third-parties)

v14.2.23

Compare Source

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

Core Changes
  • backport: force module format for virtual client-proxy (#​74590)
  • Backport: Use provided waitUntil for pending revalidates (#​74573)
  • Feature: next/image: add support for images.qualities in next.config (#​74500)
Credits

Huge thanks to @​styfle, @​ijjk and @​lubieowoce for helping!

v14.2.22

Compare Source

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

Core Changes
  • Retry manifest file loading only in dev mode: #​73900
  • Ensure workers are cleaned up: #​71564
  • Use shared worker for lint & typecheck steps: #​74154
Credits

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

v14.2.21

Compare Source

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

Core Changes
Misc Changes
Credits

Huge thanks to @​unstubbable, @​ztanner, and @​styfle for helping!

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

[!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!

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!


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 November 6, 2024 01:15
@renovate renovate bot added automerge Enable Kodiak auto-merge dependencies Change in project dependencies. kodiak: merge.method = 'squash' Kodiak will squash merge this PR. labels Nov 6, 2024
Copy link

vercel bot commented Nov 6, 2024

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

Name Status Preview Comments Updated (UTC)
inreach-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jan 23, 2025 9:05pm

Copy link
Contributor

coderabbitai bot commented Nov 6, 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 Nov 6, 2024

Copy link

relativeci bot commented Nov 6, 2024

#2143 Bundle Size — 5.64MiB (0%).

dfe8bde(current) vs 64b2b9c dev#2099(baseline)

Warning

Bundle contains 5 duplicate packages – View duplicate packages

Bundle metrics  Change 1 change
                 Current
#2143
     Baseline
#2099
No change  Initial JS 3.05MiB 3.05MiB
No change  Initial CSS 9.7KiB 9.7KiB
Change  Cache Invalidation 29.67% 24.05%
No change  Chunks 67 67
No change  Assets 80 80
No change  Modules 2016 2016
No change  Duplicate Modules 361 361
No change  Duplicate Code 10.01% 10.01%
No change  Packages 159 159
No change  Duplicate Packages 5 5
Bundle size by type  no changes
                 Current
#2143
     Baseline
#2099
No change  JS 4.4MiB 4.4MiB
No change  Other 1.13MiB 1.13MiB
No change  Fonts 94.54KiB 94.54KiB
No change  CSS 9.7KiB 9.7KiB
No change  IMG 8.57KiB 8.57KiB

Bundle analysis reportBranch renovate/next.jsProject dashboard


Generated by RelativeCIDocumentationReport issue

Copy link
Contributor

github-actions bot commented Nov 6, 2024

📦 Next.js Bundle Analysis for @weareinreach/app

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

Copy link

alwaysmeticulous bot commented Nov 6, 2024

🤖 No test run has been triggered as your Meticulous project has been deactivated (since you haven't viewed any test results in a while). Click here to reactivate.

Last updated for commit dfe8bde. This comment will update as new commits are pushed.

@renovate renovate bot force-pushed the renovate/next.js branch from bb0e85b to f9af444 Compare November 13, 2024 22:28
@renovate renovate bot changed the title chore(web): update next.js to v14.2.17 chore(web): update next.js to v14.2.18 Nov 13, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from f9af444 to c618b86 Compare December 3, 2024 18:46
@renovate renovate bot changed the title chore(web): update next.js to v14.2.18 chore(web): update next.js to v14.2.19 Dec 3, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from c618b86 to f6115e1 Compare December 4, 2024 22:46
@renovate renovate bot changed the title chore(web): update next.js to v14.2.19 chore(web): update next.js to v14.2.20 Dec 4, 2024
@renovate renovate bot changed the title chore(web): update next.js to v14.2.20 fix(web): update next.js to v14.2.20 Dec 10, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from f6115e1 to 90c1bae Compare December 19, 2024 11:42
@renovate renovate bot changed the title fix(web): update next.js to v14.2.20 fix(web): update next.js to v14.2.21 Dec 19, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from 7792242 to fa0deca Compare December 23, 2024 21:51
@renovate renovate bot force-pushed the renovate/next.js branch from fa0deca to a2d054c Compare December 26, 2024 18:19
@renovate renovate bot changed the title fix(web): update next.js to v14.2.21 fix(web): update next.js to v14.2.22 Dec 26, 2024
@renovate renovate bot force-pushed the renovate/next.js branch from a2d054c to fc70fb8 Compare January 8, 2025 14:13
@renovate renovate bot changed the title fix(web): update next.js to v14.2.22 fix(web): update next.js to v14.2.23 Jan 8, 2025
@renovate renovate bot force-pushed the renovate/next.js branch from fc70fb8 to 2ad37d5 Compare January 11, 2025 08:22
@renovate renovate bot force-pushed the renovate/next.js branch from 2ad37d5 to 2418b4f Compare January 12, 2025 07:08
@renovate renovate bot force-pushed the renovate/next.js branch from 2418b4f to e6779c3 Compare January 12, 2025 07:43
@renovate renovate bot force-pushed the renovate/next.js branch from e6779c3 to 2c92775 Compare January 15, 2025 20:35
@renovate renovate bot force-pushed the renovate/next.js branch from 2c92775 to a625010 Compare January 15, 2025 23:55
@renovate renovate bot force-pushed the renovate/next.js branch from a625010 to 7b7cd4b Compare January 16, 2025 00:40
@renovate renovate bot force-pushed the renovate/next.js branch from 7b7cd4b to d2c224f Compare January 16, 2025 05:14
@renovate renovate bot force-pushed the renovate/next.js branch from d2c224f to 151f2bb Compare January 16, 2025 06:12
@renovate renovate bot force-pushed the renovate/next.js branch from 151f2bb to 00017a9 Compare January 16, 2025 07:48
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/next.js branch from 00017a9 to dfe8bde Compare January 23, 2025 21:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants