-
Notifications
You must be signed in to change notification settings - Fork 44
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
Upgrade bitcoin to v0.31 #79
Upgrade bitcoin to v0.31 #79
Conversation
Excuse the noise, this is another go at #78 because I saw #76. This is #60 with pinning in CI. I previously handed off to @getong because he did #74 but that seems to be stalling. Lets see if I can get this past CI. I copied the pinning done by @notmandatory's PR and tweaked it a bit after upgrading the |
Upgrade: - bitcoin to v0.31.0 - miniscript to v11.0.0 Requires currently unreleased: - rust-hwi: master branch - rust-esplora-clinet: bitcoindevkit/rust-esplora-client#79
Upgrade: - bitcoin to v0.31.0 - miniscript to v11.0.0 Requires currently unreleased: - rust-hwi: master branch - rust-esplora-clinet: bitcoindevkit/rust-esplora-client#79
@@ -51,10 +51,12 @@ jobs: | |||
- name: pin dependencies | |||
if: matrix.rust.version == '1.63.0' | |||
run: | | |||
cargo update -p zstd-sys --precise "2.0.8+zstd.1.5.5" | |||
cargo update -p zstd-sys --precise "2.0.6+zstd.1.5.2" | |||
cargo update -p zstd --precise 0.11.2+zstd.1.5.2 |
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.
Why do we now require to pin zstd
individually? I think the +zstd.1.5.5
already should pin it to a particular version? Moreover, any reason why we reduce the pinned zstd-sys
version from 2.0.8 to 2.0.6?
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.
I didn't think too hard about it to be honest, I find pinning to be a total waist of brain space so I just wildly try versions until something works.
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.
Oh, I remember. I brought zstd-sys
back to be in line with the new zstd
, but like you say we may not need both. (Referring to the +1.5.2
)
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.
Yeah, I think we don't need to pin both and if pinning zstd-sys
to 2.0.8+zstd.1.5.5
is sufficient to meet the MSRV, I'd always prefer to pin to the higher version.
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.
I agree with @tnull, can we change this back to zstd-sys
and zstd
1.5.5? You can verify on crates.io that 1.5.5 is the latest version with MSRV under 1.63: https://crates.io/crates/zstd-sys/versions
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.
Changed as requested, lets let CI prove if it works for us
cargo update -p time --precise "0.3.20" | ||
cargo update -p jobserver --precise "0.1.26" | ||
cargo update -p home --precise 0.5.5 | ||
cargo update -p jobserver --precise 0.1.26 |
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.
This is pinned above already, no need to duplicate here.
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.
Ouch, I thought I remove that locally. Will re-spin, thanks.
e2cfe89
to
e41b360
Compare
I left, |
Thanks for the review @tnull! |
e41b360
to
581cfb0
Compare
Done, thanks. |
Pull Request Test Coverage Report for Build 7896060347Details
💛 - Coveralls |
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.
utACK 581cfb0
Upgrade dependencies to use the latest `rust-bitcoin v0.31`. While we are at it, bump the crate version ready for release. (Includes pinning dependencies for MSRV build in CI.)
581cfb0
to
c046047
Compare
You guys were right about the pins, thanks for pushing me. |
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.
utACK c046047
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
Upgrade dependencies to use the latest
rust-bitcoin v0.31
.While we are at it, bump the crate version ready for release.
(Includes pinning dependencies for MSRV build in CI.)