Bump ldk-node dependency#72
Conversation
|
👋 I see @joostjager was un-assigned. |
There was a problem hiding this comment.
Seems we'll need to check in a separate Cargo-minimal.lock file that we use for MSRV CI.
There was a problem hiding this comment.
Ah, I usually run cargo with our MSRV, but hadn't done so here. Should I just build using cargo +1.75.0 for any Cargo.lock updates. Not sure what the best practices are.
There was a problem hiding this comment.
Ah, I usually run
cargowith our MSRV, but hadn't done so here. Should I just build usingcargo +1.75.0for anyCargo.lockupdates. Not sure what the best practices are.
No, I think we want to keep the Cargo.lock on current stable and bump it now and then when we see a requirement. Most projects also check in a separate Cargo-minimal.lock file with the MSRV, see for example https://github.com/rust-bitcoin/rust-bitcoin/blob/master/Cargo-minimal.lock
There was a problem hiding this comment.
Was going through doing this until I got to the final dep, ldk-node, and realized it's MSRV is now 1.85 so we need to do the same in this project. This luckily solves all our problems
41f0b8e to
69ebf37
Compare
|
Thanks for taking this over @benthecarman. Feel free to squash fixups and clean up commit history as needed. |
c4539d7 to
45c1cb9
Compare
jkczyz
left a comment
There was a problem hiding this comment.
LGTM, though it seems I don't have approval power.
Strange, it says 'New changes require approval from someone other than the last pusher.', but here Ben is the latest pusher... |
45c1cb9 to
551b859
Compare
since its your PR, you can't approve it |
551b859 to
10280f3
Compare
Co-Authored-By: Jeffrey Czyz <jkczyz@gmail.com>
In ldk-node's update, it bumped its MSRV to 1.85 so we need to do the same here.
10280f3 to
0e27264
Compare
Bump `ldk-node` dependency
Bump the
ldk-nodedependency to support splicing.