search

yuki-koma2 / wedding-invitation

https://wedding-invitation-one-flax.vercel.app
0 stars 0 forks source link

chore(deps): update nextjs monorepo to v14.2.18 #71

Open renovate[bot] opened 1 month ago

renovate[bot] commented 1 month ago

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
eslint-config-next (source) 14.2.14 -> 14.2.18 age adoption passing confidence
next (source) 14.2.14 -> 14.2.18 age adoption passing confidence

Release Notes

vercel/next.js (eslint-config-next) ### [`v14.2.18`](https://redirect.github.com/vercel/next.js/compare/v14.2.17...v14.2.18) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.17...v14.2.18) ### [`v14.2.17`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.17) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.16...v14.2.17) > \[!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](https://redirect.github.com/vercel/next.js/issues/72356)) - Ensure pages/500 handles cache-control as expected ([#​72050](https://redirect.github.com/vercel/next.js/issues/72050)) ([#​72110](https://redirect.github.com/vercel/next.js/issues/72110)) - fix unhandled runtime error from generateMetadata in parallel routes ([#​72153](https://redirect.github.com/vercel/next.js/issues/72153)) ##### Credits Huge thanks to [@​huozhi](https://redirect.github.com/huozhi), [@​ztanner](https://redirect.github.com/ztanner), and [@​ijjk](https://redirect.github.com/ijjk) for helping! ### [`v14.2.16`](https://redirect.github.com/vercel/next.js/compare/v14.2.15...v14.2.16) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.15...v14.2.16) ### [`v14.2.15`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.15) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.14...v14.2.15) > \[!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](https://redirect.github.com/vercel/next.js/issues/65063) - Provide non-dynamic segments to catch-all parallel routes [#​65233](https://redirect.github.com/vercel/next.js/issues/65233) - Fix client reference access causing metadata missing [#​70732](https://redirect.github.com/vercel/next.js/issues/70732) - feat(next/image): add support for decoding prop [#​70298](https://redirect.github.com/vercel/next.js/issues/70298) - feat(next/image): add images.localPatterns config [#​70529](https://redirect.github.com/vercel/next.js/issues/70529) - fix(next/image): handle undefined images.localPatterns config in images-manifest.json - fix: Do not omit alt on getImgProps return type, ImgProps [#​70608](https://redirect.github.com/vercel/next.js/issues/70608) - \[i18n] Routing fix [#​70761](https://redirect.github.com/vercel/next.js/issues/70761) ##### Credits Huge thanks to [@​ztanner](https://redirect.github.com/ztanner), [@​agadzik](https://redirect.github.com/agadzik), [@​huozhi](https://redirect.github.com/huozhi), [@​styfle](https://redirect.github.com/styfle), [@​icyJoseph](https://redirect.github.com/icyJoseph) and [@​wyattjoh](https://redirect.github.com/wyattjoh) for helping!
vercel/next.js (next) ### [`v14.2.18`](https://redirect.github.com/vercel/next.js/compare/v14.2.17...v14.2.18) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.17...v14.2.18) ### [`v14.2.17`](https://redirect.github.com/vercel/next.js/compare/v14.2.16...v14.2.17) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.16...v14.2.17) ### [`v14.2.16`](https://redirect.github.com/vercel/next.js/compare/v14.2.15...v14.2.16) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.15...v14.2.16) ### [`v14.2.15`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.15) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.14...v14.2.15) > \[!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](https://redirect.github.com/vercel/next.js/issues/65063) - Provide non-dynamic segments to catch-all parallel routes [#​65233](https://redirect.github.com/vercel/next.js/issues/65233) - Fix client reference access causing metadata missing [#​70732](https://redirect.github.com/vercel/next.js/issues/70732) - feat(next/image): add support for decoding prop [#​70298](https://redirect.github.com/vercel/next.js/issues/70298) - feat(next/image): add images.localPatterns config [#​70529](https://redirect.github.com/vercel/next.js/issues/70529) - fix(next/image): handle undefined images.localPatterns config in images-manifest.json - fix: Do not omit alt on getImgProps return type, ImgProps [#​70608](https://redirect.github.com/vercel/next.js/issues/70608) - \[i18n] Routing fix [#​70761](https://redirect.github.com/vercel/next.js/issues/70761) ##### Credits Huge thanks to [@​ztanner](https://redirect.github.com/ztanner), [@​agadzik](https://redirect.github.com/agadzik), [@​huozhi](https://redirect.github.com/huozhi), [@​styfle](https://redirect.github.com/styfle), [@​icyJoseph](https://redirect.github.com/icyJoseph) and [@​wyattjoh](https://redirect.github.com/wyattjoh) 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 becomes conflicted, or you tick the rebase/retry checkbox.

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

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

vercel[bot] commented 1 month ago

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

Name Status Preview Comments Updated (UTC)
wedding-invitation ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 14, 2024 1:10am
coderabbitai[bot] commented 1 week ago

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

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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 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` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### Documentation and Community - Visit our [Documentation](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.