Skip to content

Conversation

@q1blue
Copy link
Collaborator

@q1blue q1blue commented Feb 1, 2026

snyk-top-banner

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

Snyk changed the following file(s):

  • packages/job-server/package.json
⚠️ Warning
Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-15104645
  111  

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

@changeset-bot
Copy link

changeset-bot bot commented Feb 1, 2026

⚠️ No Changeset found

Latest commit: fe84a13

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@gemini-code-assist
Copy link

Summary of Changes

Hello @q1blue, I'm Gemini Code Assist1! 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, focuses on enhancing the project's security by upgrading the next framework dependency. The primary goal is to mitigate a high-severity vulnerability that could lead to resource exhaustion. While the package.json has been updated, a manual step is required to synchronize the pnpm-lock.yaml file.

Highlights

  • Security Upgrade: The next dependency has been upgraded to version 15.5.10 to address a high-severity vulnerability (SNYK-JS-NEXT-15104645) related to 'Allocation of Resources Without Limits or Throttling'.
  • Automated Remediation: This pull request was automatically generated by Snyk to provide a fix for the identified security vulnerability.
  • Manual Lockfile Update Required: The pnpm-lock.yaml file could not be updated automatically and requires manual intervention before this pull request can be merged.
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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request, automatically generated by Snyk, upgrades the next package from version ^14.2.24 to ^15.5.10 to address a security vulnerability. While this is an important security fix, this major version upgrade of Next.js introduces a critical incompatibility. Next.js 15 requires React 19, but this project's dependencies for react and react-dom are still on version 17. This will break the application. Additionally, as noted in the pull request description, the pnpm-lock.yaml file needs to be updated manually. Due to the breaking change, this PR should be handled with care.

"luxon": "^3.1.0",
"mysql2": "^2.3.3",
"next": "^14.2.24",
"next": "^15.5.10",

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

critical

Upgrading next to version 15 introduces a requirement for React 19. The react and react-dom dependencies in this package.json are on version 17 (^17.0.2), which is incompatible. This will lead to build failures or runtime errors.

To resolve this, you'll need to also upgrade react and react-dom to a version compatible with Next.js 15 (e.g., 19.0.0-rc.0 or newer) and address any breaking changes from both the Next.js and React upgrades.

Given the complexity of this major version upgrade, you might consider if there's a patch version of next@14 that fixes the vulnerability, or if the usage of next can be removed if it's not essential for this job server.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants