Conversation
tcharding
force-pushed
the
08-06-bump-msrv
branch
from
c286487 to
7168078
Compare
|
As you did with other bumps, you forget to update the README 😂 |
tcharding
force-pushed
the
08-06-bump-msrv
branch
from
7168078 to
0d4dc7e
Compare
|
Damn, I have a grep alias that ignores md files - I have to remember not to use it when doing MSRV bumps. Thanks man. |
tcharding
force-pushed
the
08-06-bump-msrv
branch
from
0d4dc7e to
add2fc3
Compare
tcharding
force-pushed
the
08-06-bump-msrv
branch
from
add2fc3 to
34943ea
Compare
|
Force push is just a change to the docs on the MSRV job, sorry to require re-ack @storopoli (found while rebaseing #694). |
|
Could you add a commit to the start of this which bumps the honggfuzz dep in both lockfiles? It doesn't really have anything to do with this PR but it's a "toolchain update" and it'd simplify my local CI runs. |
tcharding
force-pushed
the
08-06-bump-msrv
branch
2 times, most recently
from
c1c7587 to
3916522
Compare
|
I'm not sure why the hongfuzz change causes |
|
6a56d37 seems weird, and it bumps the versions of stuff in Cargo-minimal.lock that should continue to work. I'd prefer you just updated And the reason why is that honggfuzz is both a dependency and a binary that the developer needs to have installed on their system, and the versions of these two things need to match exactly, and my CI scripts have the latest version since we updated rust-bitcoin and others. And also the latest version fixes a bug with |
|
Ah I see, thanks for the explanation. Will re-spin |
A recent patch version of `hongfuzz` fixed a bug with `memcpy`, we likely do not want users using the old version. Upgrade by first pinning then by patching the manifest.
As we have done in `rust-bitcoin` bump the MSVR to Rust 1.63.0 While we are at it and so that the commit lints cleanly fix a couple of new clippy warnings: - Remove redundant import of `TryFrom` - Use `then_some` combinator
Currently we are not running the MSRV job with both lock files, we should. Note also that the lock files are different, testing older versions of `hashes` and `internals` - this is because of the range dependency in `secp` (I think).
tcharding
force-pushed
the
08-06-bump-msrv
branch
from
3916522 to
c95b411
Compare
|
Want me to do a release PR? |
|
No, I just released 12.2 right before merging this. |
c95b41168933c118d0e30009ddb304f80c43f7b5 CI: Run MSRV job with both lock files (Tobin C. Harding)
d8bfe10766c63df035287f16502eb2b5db1bf8b0 Bump MSRV to Rust 1.63.0 (Tobin C. Harding)
f62bdf3ec71b932251180cc68404482442fc5e8e fuzz: Upgrade hongfuzz patch version (Tobin C. Harding)
Pull request description:
As we have done in `rust-bitcoin` bump the MSVR to Rust 1.63.0
Also, run the MSRV CI job with both lockfiles (which are currently different).
ACKs for top commit:
apoelstra:
ACK c95b41168933c118d0e30009ddb304f80c43f7b5 successfully ran local tests; glad I got #712 in first so I could do the release!
Tree-SHA512: b3ae9583f10ac2d01353736fe68a37bc0fff6774e4ea935b4fbf16bdb3cb033b4c281b8cb45d9e6ead343d2b7033d042190369cbe21b953ac392d19ff564cf1a
3 participants
As we have done in
rust-bitcoinbump the MSVR to Rust 1.63.0Also, run the MSRV CI job with both lockfiles (which are currently different).