Prepare stack of releases#638
Merged
Merged
Conversation
In preparation for release bump the version, add a changelog entry, and update the lock files.
In preparation for release bump the version, add a changelog entry, and update the lock files.
Member
Author
|
FWIW |
Just do these two together in a single patch. In preparation for release bump the version of both crates, add changelog entries, and update the lock files.
df2fd0b to
193518a
Compare
Member
Author
|
Tagged and published. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
We want to release the v31 stuff from types. Doing so requires release of the client, bitcoind, and electrsd as well.