Prepare to release version 0.16 #282
Merged
Conversation
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
adamreichold
force-pushed
the
release-0.16
branch
from
b5aba4c to
a8718e7
Compare
davidhewitt
reviewed
Mar 3, 2022
There was a problem hiding this comment.
👍 do you want yourself / me / @kngwyu to run cargo publish?
I think you have bigger fish to fry at the moment, so I will give it a try. Should also be a good test whether any permissions are still missing. |
adamreichold
force-pushed
the
release-0.16
branch
from
a8718e7 to
b0d54de
Compare
|
Looks like it worked well. Thanks for handling this! |
|
Thanks too 😃 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to #259 which also bumps our version to 0.16. However, I would like to wait doing the release until after we have decided on and possibly merged the breaking changes from #279 and #280.