[Snyk] Security upgrade jest from 29.6.0 to 30.0.0

[St0nersdash]

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
	Prototype Pollution SNYK-JS-JSYAML-13961110	545

---

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:

🦉 Prototype Pollution

[gemini-code-assist]

Summary of Changes

Hello @St0nersdash, 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, aims to enhance the project's security posture by upgrading the jest testing framework. The upgrade specifically targets and remediates a critical 'Prototype Pollution' vulnerability found in the project's npm dependencies, ensuring a more secure development environment.

Highlights

• Security Upgrade: Upgrades the jest dependency from version 29.6.0 to 30.0.0 to address identified security vulnerabilities.
• Vulnerability Fix: Resolves a 'Prototype Pollution' vulnerability (SNYK-JS-JSYAML-13961110) found in the project's npm dependencies.
• Dependency Updates: Updates package.json and package-lock.json to reflect the new jest version and associated dependency changes.

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 from Snyk upgrades jest from version 29.6.0 to 30.0.0 to address a security vulnerability. While the security fix is important, this is a major version upgrade for jest which introduces breaking changes. The current versions of related packages in your devDependencies, such as ts-jest and @types/jest, are severely outdated and will be incompatible with jest@30, which will break your test suite. I have left a critical comment with specific recommendations to update these dependencies to ensure a smooth upgrade.

[gemini-code-assist]

This pull request upgrades jest to a new major version (v30.0.0). This is a significant update with breaking changes that requires updating other related development dependencies to ensure compatibility. The current versions of ts-jest, @types/jest, and jest-circus are incompatible with Jest 30 and will cause the build to fail.

Here are the required changes:

• @types/jest: Must be upgraded to a version compatible with Jest 30. The current version ^27.0.2 is for Jest 27.
• ts-jest: Must be upgraded to a version that supports Jest 30. The current version ^27.0.5 is for Jest 27.
• jest-circus: This has been the default test runner in Jest since v27 and is bundled with jest. The explicit dependency is no longer needed and should be removed.

To fix this, you need to update your devDependencies. For example:

"devDependencies": {
  "@types/jest": "^29.5.11",
  "@types/node": "^16.11.25",
  "@types/semver": "^6.0.0",
  "@vercel/ncc": "^0.33.4",
  "jest": "^30.0.0",
  "prettier": "^1.19.1",
  "ts-jest": "^29.1.2",
  "typescript": "^3.8.3"
}

Note: The versions for @types/jest and ts-jest in the example above are the latest stable versions compatible with Jest 29. You will need to find and use versions that are specifically compatible with Jest 30. Without these updates, your tests will not run.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	jest@​29.6.0 ⏵ 30.0.0	+1		-1	+5
	semver@​7.7.1 ⏵ 7.7.3	+1		+1

View full report