fix: add Cargo.lock to project template to avoid broken dependencies #191
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By pinning new project's dependencies to specific versions, we avoid problems like #187 which are caused by changes in the dependencies (in this case we were using a prerelease version of a dependency which updated one of its dependencies to edition=2024, but this will also prevent accidental semver-breaking changes from breaking our builds, too).
This also adds a justfile that makes it easy to update the lockfile.