chore: update Jest deps to v29 in package template#7900
Merged
cryptodev-2s merged 1 commit intomainfrom Feb 11, 2026
Merged
Conversation
Missed updating the create-package template during the Jest v27 to v29 migration (#7894).
Mrtenz
approved these changes
Feb 11, 2026
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
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.
Explanation
Missed updating the create-package template during the Jest v27 to v29 migration (#7894).
References
Checklist
Note
Low Risk
Dependency-only update confined to the create-package template; risk is limited to newly generated packages’ test setup compatibility.
Overview
Updates the
scripts/create-package/package-template/package.jsondevDependencies to Jest v29 by bumpingjest,ts-jest, and@types/jestversions so new packages created from the template default to the newer test stack.Written by Cursor Bugbot for commit fc17f96. This will update automatically on new commits. Configure here.