Open renovate[bot] opened 1 week ago
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 | Nov 13, 2024 10:34pm |
[!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
tofalse
in the CodeRabbit configuration file.
New and removed dependencies detected. Learn more about Socket for GitHub โ๏ธ
๐ฎ Removed packages: npm/@next/bundle-analyzer@14.2.16, npm/@next/eslint-plugin-next@14.2.16, npm/dotenv@16.4.5, npm/escape-string-regexp@5.0.0, npm/eslint-import-resolver-typescript@3.6.3, npm/ms@2.1.3, npm/probe-image-size@7.2.3, npm/resolve-pkg-maps@1.0.0, npm/tiny-invariant@1.3.3
f9af444(current) vs 6822567 dev#1689(baseline)
[!WARNING] Bundle contains 5 duplicate packages โ View duplicate packages
Bundle metrics
2 changes
1 regression
โโโโโโโโโโ | โโโโโโCurrent #1766 |
โโโโโBaseline #1689 |
---|---|---|
Initial JS | 3.05MiB (~+0.01% ) |
3.05MiB |
Initial CSS | 9.7KiB |
9.7KiB |
Cache Invalidation | 80.31% |
30.48% |
Chunks | 67 |
67 |
Assets | 80 |
80 |
Modules | 2016 |
2016 |
Duplicate Modules | 361 |
361 |
Duplicate Code | 10% |
10% |
Packages | 159 |
159 |
Duplicate Packages | 5 |
5 |
2 changes
1 regression
1 improvement
Bundle analysis reportโBranch renovate/next.jsโProject dashboard
Generated by RelativeCIโDocumentationโReport issue
This analysis was generated by the Next.js Bundle Analysis action. ๐ค
This PR introduced no changes to the JavaScript bundle! ๐
๐ค 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 f9af444. This comment will update as new commits are pushed.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
This PR contains the following updates:
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
14.2.16
->14.2.18
Release Notes
vercel/next.js (@next/bundle-analyzer)
### [`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!vercel/next.js (@next/eslint-plugin-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!vercel/next.js (@next/third-parties)
### [`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!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!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)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.
This PR was generated by Mend Renovate. View the repository job log.