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

Prepare to release version 0.16 #282

Merged
merged 1 commit into from
Mar 3, 2022
Merged

Prepare to release version 0.16 #282

merged 1 commit into from
Mar 3, 2022

Conversation

adamreichold
Copy link
Member

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.

Copy link
Member

@davidhewitt davidhewitt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 do you want yourself / me / @kngwyu to run cargo publish?

@adamreichold
Copy link
Member Author

+1 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 adamreichold marked this pull request as ready for review March 3, 2022 21:26
@adamreichold adamreichold merged commit b9f01fa into main Mar 3, 2022
@adamreichold adamreichold deleted the release-0.16 branch March 3, 2022 21:48
@davidhewitt
Copy link
Member

Looks like it worked well. Thanks for handling this!

@kngwyu
Copy link
Member

kngwyu commented Mar 4, 2022

Thanks too 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants