-
-
Notifications
You must be signed in to change notification settings - Fork 223
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
Version Packages #605
Version Packages #605
Conversation
dd4070d
to
8bcd462
Compare
8bcd462
to
6d63ffc
Compare
Hi @SimenB 👋 |
6d63ffc
to
e730242
Compare
e730242
to
cb11bf4
Compare
I think we have to make this a major version bump because of #574 |
Yeah, that PR should have included a changeset. You can probably push a changeset separately to |
Oh I guess I misunderstood the process. I thought we pushed a changeset when we wanted to trigger a release. Which I didn't at the time. |
No, together with the changes. Then a PR like this is automatically created, and a release happens when it's merged. |
OK. I think this should do what we need: #612. If we rebase/merge that to this branch, then should be good to go. Sorry about that. |
cb11bf4
to
316f1a5
Compare
@keeganwitt if you merge this now, the release should happen |
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
jest-extended@4.0.0
Major Changes
Minor Changes
Patch Changes