-
Notifications
You must be signed in to change notification settings - Fork 261
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
Tracking PR for release 0.18.0
#313
Tracking PR for release 0.18.0
#313
Conversation
ee183d6
to
ee80db8
Compare
Other possible PRs that look ready/interesting for next release: |
I messaged @stevenroose on another platform but for transparency I'd like to know what's the status of this crate? Are you watching this repo @apoelstra? In order to upgrade |
Yeah, to upgrade bitcoind I need an upgrade here, I just merged #312 to move things forwards, but we will need steven to publish. |
9fe7f51
to
a89d803
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK a89d803
Upgrade to the recent bitcoin v0.31.0 release by doing: - Remove dependency on `bitcoin_private`, use hex stuff from `bitcoin::hex` (re-export of `hex-conservative`). - Do type renames. - Add a couple of type annotations when parsing `Address`.
Add changelog entry and bump the version number of the `json` crate.
a89d803
to
f0efe22
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK f0efe22
@@ -1367,18 +1367,22 @@ fn test_add_multisig_address(cl: &Client) { | |||
assert!(cl.add_multisig_address(addresses.len(), &addresses, None, Some(json::AddressType::Bech32)).is_ok()); | |||
} | |||
|
|||
#[rustfmt::skip] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😅
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ACK f0efe22
I'm not sure what we want to consider for merge before cutting the next release but at least we need: