Skip to content

[Snyk] Security upgrade jest from 27.0.0 to 28.0.0#149

Closed
Seismic-Security-Service wants to merge 1 commit into
masterfrom
snyk-fix-57656ebf5e17f067e635874313ae089e
Closed

[Snyk] Security upgrade jest from 27.0.0 to 28.0.0#149
Seismic-Security-Service wants to merge 1 commit into
masterfrom
snyk-fix-57656ebf5e17f067e635874313ae089e

Conversation

@Seismic-Security-Service

Copy link
Copy Markdown

snyk-top-banner

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

Snyk changed the following file(s):

  • pkgs/kona/package.json

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

⚠️ Warning
Failed to update the yarn.lock, 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-WS-17988732
  124  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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

@Seismic-Security-Service

Copy link
Copy Markdown
Author

Merge Risk: High

The upgrade from Jest v27 to v28 is a major version jump with significant breaking changes requiring configuration and code updates.

Key Breaking Changes:

  • Dependencies: jest-environment-jsdom and jest-jasmine2 are no longer included by default and must be installed separately if your project uses them.
  • Node.js & TypeScript Versions: Support for Node.js 10 and 15 is dropped. The minimum required TypeScript version is now 4.3.
  • Configuration Updates: Several configuration options have been renamed or removed:
    • testURL is removed. Use testEnvironmentOptions: { url: '...' } instead.
    • extraGlobals is renamed to sandboxInjectedGlobals.
    • timers is renamed to fakeTimers.
  • API & Behavior Changes:
    • expect.toHaveProperty() now strictly checks for property existence, not equality with undefined.
    • Direct imports of expect must now use named imports: import {expect} from 'expect';.
    • Full support for package.json exports may change how modules are resolved.

Source: Jest v27 to v28 Upgrade Guide

Recommendation: Developers must review the official upgrade guide, install the now-separate environment packages, and update their Jest configuration file (jest.config.js) and tests to align with the new API behaviors and options.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@Seismic-Security-Service

Seismic-Security-Service commented Jul 17, 2026

Copy link
Copy Markdown
Author

Snyk checks have failed. 25 issues have been found so far.

Status Scan Engine Critical High Medium Low Total (25)
Open Source Security 1 24 0 0 25 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

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

@Seismic-Security-Service

Copy link
Copy Markdown
Author

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

  • SNYK-JS-WS-17988732

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.


This action was performed automatically by Snyk.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants