chore: Update rust-version to 1.75.0 in Cargo.toml files #623
Labels
No labels
DB & Storage
Deployment
Error Handling & Logging
Maintenance
Payment Backend
backport
backport v0.13.x
backport v0.14.x
backport v0.15.x
bindings
blocked
bug
cdk-sql
ci
cli
deps
documentation
duplicate
enhancement
good first issue
help wanted
invalid
keep-open
ldk-node-ui
migrations
mint
mutation-testing
needs rebase
needs review
new nut
nut change
question
ready
rust-version
rustfmt
stacked hold
stale
testing
wallet
weekly-report
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
cashubtc/cdk!623
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "bump_msrv"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
This PR bumps the MSRV to 1.75, previously this was 1.63 (the rust version of Debian stable), while being able to support the target of Debian stable at this point it is very old and forces use to use older deps especially for gRPC related dependencies this means we may not get the newest security updates and requires many deps to be pinned. BDK has bumped the msrv of their electrum crate for these reason as well as ldk-node, while I've previously said we should try to keep 1.63 causing us all headaches (sorry), with these projects bumping I think it makes sense for us to as well.
https://github.com/bitcoindevkit/bdk/issues/1750
Notes to the reviewers
Suggested CHANGELOG Updates
CHANGED
ADDED
REMOVED
FIXED
Checklist
just final-checkbefore committingSince our msrv now supports workspace inheritance I've moved all out common deps to the workspace making it easier to ensure we don't have multiple versions. Also updates deps that were stuck on older version to to msrv ie axum tonic, swagger.
@ -260,4 +241,2 @@run: nix develop -i -L .#db_shell --command cargo build ${{ matrix.build-args }}check-wasm:name: Check WASMIs
cdk-redbmissing?@ -260,4 +241,2 @@run: nix develop -i -L .#db_shell --command cargo build ${{ matrix.build-args }}check-wasm:name: Check WASMI don't think we should commit to an MSRV with redb its too new of a project and their msrv is higher then ours and we don't want to be missing updates by pinning to an older version. In https://github.com/cashubtc/cdk/pull/623/commits/53d43b9300473a0550ddfe9c0c5265997385f6f4 I've matched the rust-version of cdk-redb to that of redb (1.81) and then added a feature to cdk-mintd so that without redb enabled it is an msrv of 1.75 and with the feature we don't commit to one.
What do you think?
@ -260,4 +241,2 @@run: nix develop -i -L .#db_shell --command cargo build ${{ matrix.build-args }}check-wasm:name: Check WASMGood point, treating it separately with a mint feature flag makes sense.