fix: package.json & package-lock.json to reduce vulnerabilities

[Dargon789]

da3d63a

Summary by Sourcery

Update dependencies and CI configuration to reduce vulnerabilities and ensure reproducible builds.

Bug Fixes:

• Address security and vulnerability concerns by upgrading application and dev dependencies to newer stable versions.

Enhancements:

• Upgrade core framework and library versions (Next.js, React, NextAuth, form validation, fonts, and related packages) to their latest compatible releases.

CI:

• Pin CircleCI Docker image to a specific cimg/base tag to make builds reproducible and more secure.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
arcjet-example	Error		Feb 7, 2026 4:04am
arcjet-example-pvhg	Error		Feb 7, 2026 4:04am

[sourcery-ai]

Reviewer's Guide

This PR updates application and tooling dependencies to newer, less vulnerable versions, aligns the lockfile with those upgrades, and pins the CircleCI base image to a specific tag for more reproducible CI builds.

Flow diagram for CircleCI job using pinned base image

flowchart TD
  developer_push[Developer pushes commit] --> github_repo[GitHub repository]
  github_repo --> circleci_pipeline[CircleCI pipeline triggers]
  circleci_pipeline --> say_hello_job[say_hello job]
  say_hello_job --> docker_executor[Docker executor]
  docker_executor --> base_image[cimg/base:2024.01]
  base_image --> steps_checkout[Checkout code]
  steps_checkout --> steps_run[Run job commands]
  steps_run --> pipeline_complete[Pipeline completes]

Loading

File-Level Changes

Change	Details	Files
Upgrade runtime and frontend dependencies to newer, presumably less vulnerable versions.	Bump all @arcjet/* packages from 1.0.0-beta.9 to 1.1.0. Update font packages, form/resolver utilities, and css-anchor-positioning to their latest specified minor versions. Upgrade Next.js, next-auth, React, React DOM, react-hook-form, and Zod to newer releases compatible with the app.	package.json
Upgrade development and tooling dependencies.	Update @playwright/test, @types/react, @types/react-dom, sass, and typescript to newer versions while retaining @types/node version. Ensure dev tooling versions better match the updated React/Next stack.	package.json
Pin the CircleCI base image to a specific version for reproducible CI builds.	Replace the CircleCI Docker image tag from cimg/base:current to cimg/base:2024.01. Clarify the comment to recommend pinning the image for reproducible builds. Relocate CI configuration into .github/config.yml.	.github/config.yml
Regenerate package-lock.json to reflect updated dependency graph.	Update all resolved versions and integrity hashes in the lockfile to match the new dependency versions. Remove outdated package resolutions and add any new transitive dependencies introduced by the upgrades.	package-lock.json

Possibly linked issues

• [Snyk] Security upgrade @playwright/test from 1.54.1 to 1.55.1 #7: PR updates @playwright/test (to 1.58.2), fulfilling the security upgrade requested for 1.55.1 in the issue.
• deps: bump next-auth from 5.0.0-beta.29 to 5.0.0-beta.30 #45: The PR includes the requested next-auth bump to 5.0.0-beta.30, directly fulfilling the Dependabot issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[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 primarily focuses on a comprehensive update of the project's dependencies to their latest stable versions. This effort aims to mitigate potential security vulnerabilities, enhance performance, and ensure compatibility with modern development practices. Additionally, the CI/CD configuration has been refactored, indicating a move towards more explicit and reproducible build environments.

Highlights

• Dependency Updates: Numerous dependencies and devDependencies across package.json and package-lock.json have been updated to their latest versions. This includes core frameworks like next, react, and next-auth, as well as various @arcjet and @fontsource libraries, addressing potential vulnerabilities and improving stability.
• CI/CD Configuration Refactoring: The CI configuration file has been renamed from .circleci/config.yml to .github/config.yml, suggesting a potential migration or alignment with GitHub Actions. Additionally, the base Docker image for CI has been pinned to a specific version (cimg/base:2024.01) for more reproducible builds.
• Package Additions and Removals: Several unused or deprecated packages, such as @swc/counter, busboy, color and its related dependencies, is-arrayish, simple-swizzle, streamsearch, and undici, have been removed from package-lock.json. New packages like @arcjet/body, @img/colour, baseline-browser-mapping, and specific sharp platform-specific packages for RISC-V architecture have been added.
• Node.js Engine Requirements: The minimum Node.js version requirements have been updated for several packages, including next and various @arcjet modules, now requiring Node.js >=20 or >=20.9.0.

Changelog

• .circleci/config.yml
  • Renamed to .github/config.yml.
  • Updated the cimg/base Docker image from current to 2024.01 for reproducible builds.
• package-lock.json
  • Updated @arcjet/decorate from 1.0.0-beta.9 to 1.1.0.
  • Updated @arcjet/env from 1.0.0-beta.9 to 1.1.0.
  • Updated @arcjet/ip from 1.0.0-beta.9 to 1.1.0.
  • Updated @arcjet/next from 1.0.0-beta.9 to 1.1.0.
  • Updated @fontsource-variable/figtree from 5.2.8 to 5.2.10.
  • Updated @fontsource/ibm-plex-mono from 5.2.6 to 5.2.7.
  • Updated @hookform/resolvers from 5.1.1 to 5.2.2.
  • Updated @nosecone/next from 1.0.0-beta.9 to 1.1.0.
  • Updated @oddbird/css-anchor-positioning from 0.6.1 to 0.8.0.
  • Updated next from 15.3.8 to 16.1.6.
  • Updated next-auth from 5.0.0-beta.29 to 5.0.0-beta.30.
  • Updated react from 19.1.0 to 19.2.4.
  • Updated react-dom from 19.1.0 to 19.2.4.
  • Updated react-hook-form from 7.60.0 to 7.71.1.
  • Updated zod from 3.25.76 to 4.3.6.
  • Updated @playwright/test from 1.54.1 to 1.58.2.
  • Updated @types/react from 19.1.8 to 19.2.13.
  • Updated @types/react-dom from 19.1.6 to 19.2.3.
  • Updated sass from 1.89.2 to 1.97.3.
  • Updated typescript from 5.8.3 to 5.9.3.
  • Removed @swc/counter, @fastify/busboy, busboy, color, color-convert, color-name, color-string, is-arrayish, simple-swizzle, streamsearch, and undici packages.
  • Added @arcjet/body, @img/colour, baseline-browser-mapping, @img/sharp-libvips-linux-riscv64, and @img/sharp-linux-riscv64.
  • Node.js engine requirements for @arcjet/* packages and nosecone were updated from >=18 to >=20.
  • The next package's Node.js engine requirement was updated from ^18.18.0 || ^19.8.0 || >= 20.0.0 to >=20.9.0.
  • Peer dependency for next-auth was updated to include next: ^14.0.0-0 || ^15.0.0 || ^16.0.0 and nodemailer: ^7.0.7.
  • Removed dev: true flags from several optional dependencies.
• package.json
  • Updated @arcjet/decorate from 1.0.0-beta.9 to 1.1.0.
  • Updated @arcjet/env from 1.0.0-beta.9 to 1.1.0.
  • Updated @arcjet/ip from 1.0.0-beta.9 to 1.1.0.
  • Updated @arcjet/next from 1.0.0-beta.9 to 1.1.0.
  • Updated @fontsource-variable/figtree from 5.2.8 to 5.2.10.
  • Updated @fontsource/ibm-plex-mono from 5.2.6 to 5.2.7.
  • Updated @hookform/resolvers from 5.1.1 to 5.2.2.
  • Updated @nosecone/next from 1.0.0-beta.9 to 1.1.0.
  • Updated @oddbird/css-anchor-positioning from 0.6.1 to 0.8.0.
  • Updated next from 15.3.8 to 16.1.6.
  • Updated next-auth from 5.0.0-beta.29 to 5.0.0-beta.30.
  • Updated react from 19.1.0 to 19.2.4.
  • Updated react-dom from 19.1.0 to 19.2.4.
  • Updated react-hook-form from 7.60.0 to 7.71.1.
  • Updated zod from 3.25.76 to 4.3.6.
  • Updated @playwright/test from 1.54.1 to 1.58.2.
  • Updated @types/node (no version change, but listed in diff).
  • Updated @types/react from 19.1.8 to 19.2.13.
  • Updated @types/react-dom from 19.1.6 to 19.2.3.
  • Updated sass from 1.89.2 to 1.97.3.
  • Updated typescript from 5.8.3 to 5.9.3.

Activity

• No human activity (comments, reviews, etc.) has been recorded for this pull request since its creation.

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. ↩

[sourcery-ai]

Hey - I've left some high level feedback:

• Moving the CircleCI config from .circleci/config.yml to .github/config.yml will prevent CircleCI from picking it up; unless you're intentionally decommissioning CircleCI, keep the config under .circleci/config.yml.
• Several dependencies were bumped across major versions (e.g., next 15→16, zod 3→4, react-hook-form 7.60→7.71); verify and include any necessary code or configuration changes required by these upgrades in this PR so the app aligns with the new APIs.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Moving the CircleCI config from `.circleci/config.yml` to `.github/config.yml` will prevent CircleCI from picking it up; unless you're intentionally decommissioning CircleCI, keep the config under `.circleci/config.yml`.
- Several dependencies were bumped across major versions (e.g., `next` 15→16, `zod` 3→4, `react-hook-form` 7.60→7.71); verify and include any necessary code or configuration changes required by these upgrades in this PR so the app aligns with the new APIs.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request effectively updates numerous dependencies across package.json and package-lock.json, which aligns with the goal of reducing vulnerabilities. Pinning the CircleCI Docker image version in the configuration is also a commendable change for ensuring reproducible builds. However, I've identified a critical issue where the CircleCI configuration file has been incorrectly moved to the .github directory, which will likely break your CI pipeline. Please see the detailed comment for the fix.

[gemini-code-assist]

This file appears to be a CircleCI configuration, but it has been moved to the .github directory, which is used for GitHub Actions. This will likely break your CI pipeline as CircleCI will no longer find its configuration file at the expected .circleci/config.yml path. If you intend to continue using CircleCI, this file should be moved back to its original location.