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

Missing Cargo.lock #37

Closed
Kranzes opened this issue Nov 7, 2024 · 2 comments · Fixed by #65
Closed

Missing Cargo.lock #37

Kranzes opened this issue Nov 7, 2024 · 2 comments · Fixed by #65
Assignees
Milestone

Comments

@Kranzes
Copy link

Kranzes commented Nov 7, 2024

Can you please remove Cargo.lock for gitignore and commit a Cargo.lock that's been verified to work with the crates?

@devigned
Copy link
Contributor

devigned commented Nov 8, 2024

Hyperlight is intended to be used as a library. I don't think we would want to check in the Cargo.lock since that would constrain folks taking a library dependency on the project.

@devigned devigned closed this as completed Nov 8, 2024
@eddyb
Copy link

eddyb commented Nov 13, 2024

Hyperlight is intended to be used as a library. I don't think we would want to check in the Cargo.lock since that would constrain folks taking a library dependency on the project.

Please see https://blog.rust-lang.org/2023/08/29/committing-lockfiles.html, the official policy/recommendation on this matter has changed.

Cargo.lock in the git repo does not affect downstream users, but rather serves as a way to track known-working (as verified by CI) combinations of dependencies during development.

You can also add a "test after cargo update" step in CI, if you're concerned about issues arising from newer otherwise-semver-compat versions of dependencies etc.

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 a pull request may close this issue.

4 participants