You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
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.
Can you please remove Cargo.lock for gitignore and commit a Cargo.lock that's been verified to work with the crates?
The text was updated successfully, but these errors were encountered: