Production deployment #370
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [next](https://nextjs.org) ([source](https://redirect.github.com/vercel/next.js)) | [`14.2.15` -> `14.2.21`](https://renovatebot.com/diffs/npm/next/14.2.15/14.2.21) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | ### GitHub Vulnerability Alerts #### [CVE-2024-56332](https://redirect.github.com/vercel/next.js/security/advisories/GHSA-7m27-7ghc-44w9) ### Impact A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. _Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time._ Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. ### Patches This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version. ### Workarounds There are no official workarounds for this vulnerability. ### Credits Thanks to the PackDraw team for responsibly disclosing this vulnerability. --- ### Release Notes <details> <summary>vercel/next.js (next)</summary> ### [`v14.2.21`](https://redirect.github.com/vercel/next.js/compare/v14.2.20...v14.2.21) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.20...v14.2.21) ### [`v14.2.20`](https://redirect.github.com/vercel/next.js/compare/v14.2.19...ed78a4aa673034719d5664536a80d326eebac7e1) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.19...v14.2.20) ### [`v14.2.19`](https://redirect.github.com/vercel/next.js/releases/tag/v14.2.19) [Compare Source](https://redirect.github.com/vercel/next.js/compare/v14.2.18...v14.2.19) > \[!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](https://redirect.github.com/vercel/next.js/issues/73433)) - Increase max cache tags to 128 ([#​73125](https://redirect.github.com/vercel/next.js/issues/73125)) ##### Misc Changes - Update max tag items limit in docs ([#​73445](https://redirect.github.com/vercel/next.js/issues/73445)) ##### Credits Huge thanks to [@​ztanner](https://redirect.github.com/ztanner) and [@​ijjk](https://redirect.github.com/ijjk) for helping! ### [`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) </details> --- ### Configuration 📅 **Schedule**: Branch creation - "" in timezone Europe/Berlin, Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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 this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/simonknittel/simonknittel.de). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOS44NS4wIiwidXBkYXRlZEluVmVyIjoiMzkuODUuMCIsInRhcmdldEJyYW5jaCI6ImRldmVsb3AiLCJsYWJlbHMiOltdfQ==--> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Only merge using a merge commit!