Bump jest to v30 #23
Open
Bump jest to v30 #23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
soranakahara
force-pushed
the
update-jest
branch
from
f4db6a5 to
3c67bef
Compare
kazuma0129
approved these changes
Oct 1, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Upgrade Jest to v30.1.3 to address security vulnerabilities. (https://github.com/line/liff-mock/security/dependabot/83)
To fully address this security alert, we also need to update the liff-sdk to version 2.27.1 or later. I will update the liff-sdk in the next PR.
During the migration to Jest v30, some aliases were removed, so I replaced them. (https://jestjs.io/docs/upgrading-to-jest30#removal-of-alias-matcher-functions)