[Snyk] Security upgrade @arcjet/next from 1.0.0-beta.10 to 1.1.0

[Dargon789]

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• package.json
• package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-UNDICI-14943963	479

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

[Dargon789]

❌ Deploy Preview for heroic-nougat-6c8a7f failed. Why did it fail? →

Name	Link
🔨 Latest commit	f01a278
🔍 Latest deploy log	https://app.netlify.com/projects/heroic-nougat-6c8a7f/deploys/698778345cef9e000802aa19

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[gemini-code-assist]

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request, automatically generated by Snyk, implements a crucial security upgrade for the project's npm dependencies. It primarily focuses on updating the @arcjet/next package and its associated @arcjet ecosystem from version 1.0.0-beta.10 to 1.1.0. This update is designed to mitigate a medium-severity vulnerability identified as "Allocation of Resources Without Limits or Throttling" (SNYK-JS-UNDICI-14943963). The changes also involve an increase in the minimum required Node.js version for several updated packages and a minor adjustment to the next framework dependency.

Highlights

• Security Vulnerability Fix: This pull request addresses a medium-severity 'Allocation of Resources Without Limits or Throttling' vulnerability (SNYK-JS-UNDICI-14943963) by upgrading affected dependencies.
• Dependency Upgrade: The @arcjet/next package, along with several other @arcjet/* packages and arcjet itself, have been upgraded from version 1.0.0-beta.10 to 1.1.0.
• Node.js Engine Requirement Update: The minimum Node.js version requirement for many @arcjet/* packages has been increased from >=18 to >=20.
• Dependency Resolution Refactoring: Changes in package-lock.json indicate a refactoring of how certain transitive dependencies (e.g., @connectrpc/connect-node, @connectrpc/connect-web, @fastify/busboy, undici) are resolved, moving them from top-level to nested within the updated @arcjet packages.

Changelog

• package-lock.json
  • Numerous @arcjet/* packages (e.g., @arcjet/analyze, @arcjet/analyze-wasm, @arcjet/duration, @arcjet/env, @arcjet/headers, @arcjet/logger, @arcjet/protocol, @arcjet/runtime, @arcjet/stable-hash) and the arcjet package have been upgraded from 1.0.0-beta.10 to 1.1.0.
  • The minimum Node.js engine requirement for these @arcjet/* packages has been raised from >=18 to >=20.
  • The next dependency version has been explicitly pinned to 15.5.9 from ^15.5.9.
  • Several transitive dependencies, including @connectrpc/connect-node, @connectrpc/connect-web, @fastify/busboy, and undici, are no longer listed as top-level dependencies, indicating a change in how they are resolved and managed by the updated @arcjet packages.
• package.json
  • The @arcjet/next dependency has been updated from 1.0.0-beta.10 to 1.1.0.

Activity

• Snyk automatically created this pull request to address identified security vulnerabilities.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the @arcjet/next package from 1.0.0-beta.10 to 1.1.0 to resolve a security vulnerability. The update is necessary and correctly applied. However, the automated change only targets the @arcjet/next package, leaving other related @arcjet/* packages at the older version. This can result in multiple versions of the same dependencies being included in the project, which is suboptimal. I have provided a suggestion to update all @arcjet/* packages to version 1.1.0 to maintain consistency and avoid potential issues.

[Dargon789]

#61