Skip to content

[Snyk] Security upgrade jest from 29.7.0 to 30.0.0 - #92

Open
snyk-io[bot] wants to merge 2 commits into
mainfrom
snyk-fix-e66acede94c68c231bdafe4cea609e7d
Open

snyk-io[bot] wants to merge 2 commits into
mainfrom
snyk-fix-e66acede94c68c231bdafe4cea609e7d

Conversation

@snyk-io

@snyk-io snyk-io Bot commented Jul 2, 2026 •

Copy link
Copy Markdown

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • packages/sdk-core/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650
medium severity Inefficient Algorithmic Complexity
SNYK-JS-JSYAML-17342520

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


This change is Reviewable

@snyk-io

snyk-io Bot commented Jul 2, 2026

Copy link
Copy Markdown
Author

Merge Risk: High

The upgrade to Jest v30.0.0 is a major version with numerous breaking changes that will require developer action, code modifications, and configuration updates.

Key Breaking Changes:

  • Environment Support: Support for Node.js versions 14, 16, 19, and 21 has been dropped. The minimum required TypeScript version is now 5.4.
  • jest-environment-jsdom Upgrade: The underlying jsdom library was upgraded from v21 to v26. This introduces significant changes, most notably making it impossible to mock window.location using Object.defineProperty. Tests relying on this pattern will break.
  • Removed API Aliases: Deprecated expect aliases have been removed (e.g., toBeCalled() is now toHaveBeenCalled()). Code using these aliases must be updated. An autofixer is available via eslint-plugin-jest.
  • Snapshot Updates Required: The format of snapshot files has changed, which will require all existing snapshots to be updated upon upgrade.
  • CLI Flag Renamed: The --testPathPattern command-line argument has been renamed to --testPathPatterns. Any scripts using the old flag must be updated.
  • Matcher Behavior: The toEqual matcher and others now exclude non-enumerable properties by default, which could alter the outcome of existing assertions.

Recommendation: This upgrade involves mandatory code and configuration changes. Developers should review the official migration guide, run the eslint-plugin-jest autofixer for alias updates, and be prepared to update all snapshots. Special attention should be paid to tests that mock window.location as they will require refactoring.

Source: Jest 30 Release Notes

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

@changeset-bot

changeset-bot Bot commented Jul 2, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 74b449c

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

@snyk-io

snyk-io Bot commented Jul 2, 2026 •

Copy link
Copy Markdown
Author

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine 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.

@snyk-io

snyk-io Bot commented Jul 2, 2026 •

Copy link
Copy Markdown
Author

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine 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.

@socket-security

Copy link
Copy Markdown

"@types/jest": "^29.5.1",
"concurrently": "^8.2.2",
"jest": "^29.5.0",
"jest": "^30.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

WARNING: jest upgraded to ^30.0.0 but @types/jest stays at ^29.5.1 and ts-jest stays at ^29.1.0

Jest 30 is a major version with breaking API changes. The remaining v29 type definitions and ts-jest transformer are likely incompatible, which can cause TypeScript type errors and test execution failures.


Reply with @kilocode-bot fix it to have Kilo Code address this issue.

@kilo-code-bot

kilo-code-bot Bot commented Jul 8, 2026 •

Copy link
Copy Markdown

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity Count
WARNING 1
Issue Details (click to expand)

WARNING

File Line Issue
packages/sdk-core/package.json 44 jest upgraded to ^30.0.0 but @types/jest stays at ^29.5.1 and ts-jest stays at ^29.1.0
Files Reviewed (1 file)
  • packages/sdk-core/package.json - 1 issue

Fix these issues in Kilo Cloud


Reviewed by step-3.7-flash-20260528 · Input: 75.7K · Output: 8.4K · Cached: 265.7K

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.

1 participant