fix vercel link

[Dargon789]

Summary by Sourcery

Update frontend dependencies and tooling to newer versions and remove an obsolete GitHub configuration file.

Enhancements:

• Bump various runtime dependencies including Arcjet, font packages, form handling, validation, and React to newer versions.
• Update development tooling dependencies such as Playwright, React type definitions, and Sass to more recent versions.

Chores:

• Remove the deprecated .github/config.yml configuration file from the repository.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
arcjet-example	Canceled		Feb 7, 2026 5:09am
arcjet-example-pvhg	Canceled		Feb 7, 2026 5:09am

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates several frontend and tooling dependencies to newer minor/patch versions and removes a GitHub configuration file, likely to align the project with current packages and deployment configuration (e.g., Vercel).

File-Level Changes

Change	Details	Files
Update core Arcjet, Nosecone, fonts, form, validation, React, and related app dependencies to newer minor/patch versions.	Bump @arcjet/* packages from 1.0.0-beta.9 to 1.1.0 for decorate, env, and ip Update @nosecone/next from 1.0.0-beta.9 to 1.1.0 Refresh UI-related libraries including fontsource packages and css-anchor-positioning to newer versions Upgrade react and react-dom to 19.2.4, and react-hook-form to 7.71.1 Upgrade zod validation library from 4.2.1 to 4.3.6	package.json package-lock.json
Update development and testing tooling versions.	Upgrade @playwright/test from 1.55.1 to 1.58.2 Update React type definitions @types/react and @types/react-dom to later 19.2.x versions Upgrade sass from 1.89.2 to 1.97.3	package.json package-lock.json
Remove GitHub configuration file no longer needed for CI or repo automation.	Delete .github/config.yml configuration file from the repository	.github/config.yml

---

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 updates a wide array of project dependencies to their latest stable versions, ensuring the application benefits from the newest features, performance improvements, and security patches. Additionally, it removes an obsolete CircleCI configuration file, simplifying the project's continuous integration setup.

Highlights

• Dependency Updates: Numerous project dependencies, including @arcjet/* packages, React, Playwright, Zod, and various font and form-related libraries, have been updated to their latest versions.
• CI/CD Configuration Removal: The .github/config.yml file, which contained CircleCI configuration, has been removed, indicating a potential shift or simplification in the continuous integration setup.
• Package Lock File Refinement: The package-lock.json file reflects the updated dependency tree, including the removal of several nested dependency entries and adjustments to 'dev' flags for optional packages, streamlining the dependency resolution.

Changelog

• .github/config.yml
  • Removed the CircleCI configuration file.
• package-lock.json
  • Updated numerous package versions across various categories (e.g., @arcjet, React, Playwright, Zod, fonts, form resolvers).
  • Removed nested node_modules entries for @arcjet related packages and protobuf/connectrpc.
  • Adjusted 'dev' flags for several optional dependencies.
• package.json
  • Bumped versions for core dependencies like @arcjet/decorate, @arcjet/env, @arcjet/ip, @fontsource-variable/figtree, @fontsource/ibm-plex-mono, @hookform/resolvers, @nosecone/next, @oddbird/css-anchor-positioning, react, react-dom, react-hook-form, and zod.
  • Updated dev dependencies including @playwright/test, @types/react, @types/react-dom, and sass.

Activity

• No specific activity (comments, reviews, progress updates) has been recorded for this pull request yet.

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:

• Removing .github/config.yml is a notable change unrelated to dependency bumps; if this file is still referenced by any GitHub workflows or tooling, consider either restoring it or replacing its configuration in the new expected location.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Removing `.github/config.yml` is a notable change unrelated to dependency bumps; if this file is still referenced by any GitHub workflows or tooling, consider either restoring it or replacing its configuration in the new expected location.

---

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 updates several dependencies to newer versions and removes an obsolete CircleCI configuration file. The dependency updates are a good maintenance task, moving some packages from beta to stable versions and fixing a version mismatch between react and react-dom. I've added one comment in package.json suggesting the use of caret ranges for dependencies to improve maintainability by allowing automatic non-breaking updates. The pull request title 'fix vercel link' does not seem to reflect the changes made; you might consider updating it for clarity.

[gemini-code-assist]

Many dependencies in this package.json are pinned to exact versions (e.g., "@arcjet/decorate": "1.1.0"). While this ensures reproducible builds, it prevents you from automatically receiving non-breaking bug fixes and security patches.

For better maintainability, consider using caret (^) ranges for most of your dependencies, especially for stable releases. This allows npm or yarn to install the latest compatible versions.

For example:
"@arcjet/decorate": "^1.1.0"

This suggestion applies to the following updated dependencies:

• @arcjet/decorate
• @arcjet/env
• @arcjet/ip
• @hookform/resolvers
• @nosecone/next
• @oddbird/css-anchor-positioning
• react-hook-form
• zod
• @playwright/test
• @types/react
• @types/react-dom
• sass

You might want to keep experimental or beta packages like next, next-auth, react, and react-dom pinned for stability.