Skip to content

Upgrade Cargo.lock to version=4 #8265

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

Draft
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

nepet
Copy link
Collaborator

@nepet nepet commented May 5, 2025

This PR upgrades Cargo.lock to version 4 . The lockfile version has changed with cargo v1.78 . Upgrading allows to use the stable toolchain which is above v1.77.

This includes upgading nixpkgs to a version that includes newer versions of rustc.

nepet added 2 commits May 5, 2025 15:23
cctools have been moved into the darwin system packages

Signed-off-by: Peter Neuroth <[email protected]>
Update Cargo.lock and nixpkgs to support current stable rust releases.
We need to update as upgrading rustc past v1.77 changes the syntax used
in for the lockfile.

Changelog-None

Signed-off-by: Peter Neuroth <[email protected]>
@nepet nepet force-pushed the 2518-upgrade-cargo-version branch from 5a4388d to 469b332 Compare May 5, 2025 13:36
@daywalker90
Copy link
Contributor

I don't quite understand what you mean by "upgrading lock file version allows using the stable toolchain". You can use version 3 just fine with the most up to date stable rust 1.86. But this would raise the minimum required rust version to 1.78, raising it from CLN's current 1.75.

@nepet
Copy link
Collaborator Author

nepet commented May 6, 2025

While it is true that cargo 1.86 is backwards compatible, the problem I headed into a couple of times so far is, that if you add a new dependency or update an existing one using any version post 1.77 the version of the lockfile will get updated (if you forget to specify the correct toolchain). The intension of this PR is to make this change visible instead of hiding it in some other PR that updates or adds a crate.

Is there a reason I am not aware of, why we want to keep staying on this specific version of rust, which is EOL since 1 year (nixpkgs v24.05 only got security updates until dec 2024 as well)?

@daywalker90
Copy link
Contributor

A few more users must install rustup since their package manager doesn't have a more recent version of rust. CLN seems to be focused on ubuntu a little and both ubuntu LTS versions 22.04 and 24.04 ship with 1.75. But if you ask me alot of people do that already and have to even, all stable debian versions ship with <1.70 for example. So if you ask me, go hard or go home: MSRV=latest stable 😄

@daywalker90
Copy link
Contributor

Btw to build all our dependency tree after running cargo update right now we would need atleast 1.82

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants