chore: track Cargo.lock for reproducible builds, fix security contact#5
Merged
TheAbMehta merged 1 commit intomasterfrom Feb 17, 2026
Merged
Conversation
- Remove Cargo.lock from .gitignore — this is a binary project, not a library, so Cargo.lock should be committed for reproducible builds per Rust guidelines - Track Cargo.lock to ensure all contributors and CI build with identical deps - Update SECURITY.md with actual vulnerability reporting link (was 'TBD')
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Cargo.lockfor reproducible builds. This was incorrectly in.gitignore.Why This Matters
Without
Cargo.lock, everycargo buildcould pull different dependency versions, causing "works on my machine" issues. This is especially important for a game client where deterministic builds matter.