-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Prepare 16.1.0 #7415
Prepare 16.1.0 #7415
Conversation
885830f
to
a611f7f
Compare
a611f7f
to
6a4832c
Compare
We can just add the changeset manually before releasing, I don't think we should edit this PR manually which is generated by changesets automatically. |
This should be done by another PR, right? If doing so, I'm worried that a PR link would become a different one from #7366. |
Yes, and then we can change the PR link before we finally merge this PR. |
Sounds good. I've pushed 548b221 directly to |
6a4832c
to
1618c29
Compare
bfc25cd
to
a6f1629
Compare
a6f1629
to
2ee2cb5
Compare
2ee2cb5
to
1d29c96
Compare
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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