Skip to content
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

Migrate Jest to v27 #10159

Closed
viceice opened this issue May 26, 2021 · 1 comment · Fixed by #10160
Closed

Migrate Jest to v27 #10159

viceice opened this issue May 26, 2021 · 1 comment · Fixed by #10160
Assignees
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress Someone is working on implementation type:refactor Refactoring or improving of existing code

Comments

@viceice
Copy link
Member

viceice commented May 26, 2021

Might be a good idea to update our jest monorepo and jest-ts test stuff once that hits 7 stabilityDays.

For easy reference, here's the blog post from Jest themselves explaining the changes.

https://jestjs.io/blog/2021/05/25/jest-27

Originally posted by @HonkingGoose in #2958 (comment)

This was referenced May 26, 2021
@HonkingGoose HonkingGoose added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others type:refactor Refactoring or improving of existing code status:in-progress Someone is working on implementation labels May 26, 2021
@renovate-release
Copy link
Collaborator

🎉 This issue has been resolved in version 25.31.12 🎉

The release is available on:

Your semantic-release bot 📦🚀

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others status:in-progress Someone is working on implementation type:refactor Refactoring or improving of existing code
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants