docs: add upgrading guide

[mrazauskas]

Summary

Jest v28 will have many breaking changes. Adding an upgrade guide would help users to refactor their tests.

Test plan

Green CI and preview on Netlify.

[SimenB]

Great stuff! can you add something for #12638 as well?

[mrazauskas]

Great stuff! can you add something for #12638 as well?

Surely. I am trying to include as much as possible. Working on that (;

[SimenB]

Happy to land as is once prettier is happy, and just make sure to circle back before releasing a stable version 🙂

[SimenB]

Great stuff! I'll probably add a section for new features people can use (making this a "what's new" thing), but this is a great start, thank you so much!

[SimenB]

I assume @types/jest will be updated. Something about "until @types/jest@28 is released"?

[mrazauskas]

Yes, updating @types/jest would be the best. I just think, if that will be fixed, we will be adding it upgrading guide. Sort-of: "you should use this version of @types/jest". So this note will disappear naturally. Perhaps?

[SimenB]

Reasonable 👍

[mrazauskas]

I'll probably add a section for new features people can use (making this a "what's new" thing), but this is a great start, thank you so much!

Yes, I was thinking about "What's New". That would work with version docs nicely as well. Will do it as separate PR.

[SimenB]

Will make the blog post more of an highlights, which is nice. Prose for blog posts are always a pain 😅

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.