Skip to content
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

Bump lockfile version #41

Merged
merged 1 commit into from
Feb 6, 2024
Merged

Bump lockfile version #41

merged 1 commit into from
Feb 6, 2024

Conversation

nmasur
Copy link
Contributor

@nmasur nmasur commented Feb 5, 2024

The Cargo.toml and Cargo.lock are out of sync. This creates an issue when attempting to build the output while locked:

cargo build --locked
    Updating crates.io index
error: the lock file Cargo.lock needs to be updated but --locked was passed to prevent this
If you want to try to generate the lock file without accessing the network, remove the --locked flag and use --offline instead.

Building while locked is important for some tooling, such as packaging with Nix. To fix this, just need to run cargo update -w.

The Cargo.toml and Cargo.lock are out of sync. This creates an issue
when attempting to build the output while locked:

cargo build --locked
    Updating crates.io index
error: the lock file Cargo.lock needs to be updated but --locked was
passed to prevent this
If you want to try to generate the lock file without accessing the
network, remove the --locked flag and use --offline instead.

Building while locked is important for some tooling, such as packaging
with Nix. To fix this, just need to run `cargo update -w`.
@robenkleene robenkleene merged commit 10510d4 into robenkleene:main Feb 6, 2024
1 check passed
@robenkleene
Copy link
Owner

Thanks for the PR. To avoid this issue in the future I'll start running cargo update -w when I bump the rep version number (seems like not doing so is what caused the issue here). Also probably a good idea to run it right before publishing a new version, just to make sure there's no difference.

Let me know if there's anything else I should be doing. Cheers!

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