chore: Cargo.lock を .gitignore から除外解除してコミット [dependency-management-005] - #1
Open
upstream-security-scan-app[bot] wants to merge 1 commit into
Open
chore: Cargo.lock を .gitignore から除外解除してコミット [dependency-management-005]#1upstream-security-scan-app[bot] wants to merge 1 commit into
upstream-security-scan-app[bot] wants to merge 1 commit into
Conversation
![security-scan[bot]](https://github.githubassets.com/images/gravatars/gravatar-user-420.png){kind=avatar}
…ement-005] Cargo.lock was listed in .gitignore, preventing reproducible builds. Remove the exclusion and commit the generated lock file so all contributors and CI use identical dependency versions.
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
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.
概要
.gitignoreにCargo.lockが記載されており、ロックファイルがリポジトリに存在しない状態を修正します。この PR はセキュリティスキャンツールによる自動修正です。
dependency-management-005: Cargo.lock が存在しない・コミットされていない
重要度: Critical
Cargo.lockが.gitignoreで除外されているため、ビルドごとに依存バージョンが再解決されます。悪意あるパッケージバージョンが公開された場合、次回のビルドで自動的に混入するリスクがあります。参考: https://doc.rust-lang.org/cargo/guide/cargo-toml-vs-cargo-lock.html
変更内容
.gitignoreからCargo.lockの除外エントリを削除cargo generate-lockfile（Rust 1.93.0）で生成したCargo.lockをコミット対象箇所
.gitignoreCargo.lockCargo.lock確認事項
cargo buildがエラーなく完了することを確認