Skip to content

chore(dep): update jest to v30.0.5 #2880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

blacksrc
Copy link
Contributor

@blacksrc blacksrc commented Aug 5, 2025

Description

This PR updates Jest to the latest stable version (v30.0.5). The update brings improved test stability, bug fixes, and performance enhancements. After the update, all tests pass successfully, with a minor adjustment changing toThrowError to toThrow. Also, ran the Prettier command, which automatically updated the formatting of some files

Related issue: #2879

Type of change

  • Chore (dependency update)
  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Ran full test suite with Jest v30.0.5
  • Verified no breaking changes except minor matcher update (toThrowErrortoThrow)
  • Fixed some formatting by running prettier command.

Test Environment:

  • OS: Ubuntu 24.04.3 LTS
  • NodeJS: v22.18.0

Checklist:

  • I have followed the contributing guidelines and style standards of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation (not applicable)
  • My changes generate no new warnings
  • All existing and new tests pass locally with my changes
  • Any dependent changes have been merged and published in downstream modules

Further comments

Considered switching to Vitest for speed and reliability, but it is out of scope for this PR.

@blacksrc
Copy link
Contributor Author

@ardatan would appreciate if you could take a look :)

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.

1 participant