Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
58 changes: 43 additions & 15 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,7 @@ natord = "1.0.9"
tempfile = "3.27.0"
path-absolutize = "3.1.1"
similar = "2.7.0"
sha2 = "0.10.9"
sha2 = "0.11.0"
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Update Buck vendoring alongside sha2 version bump

Changing sha2 to 0.11.0 in Cargo metadata does not update the Buck build graph: BUCK still depends on //third-party/rust/crates/sha2/0.10.9:sha2 (line 59), and the vendored tree only contains third-party/rust/crates/sha2/0.10.9. I checked .github/workflows/base.yml and the build job runs buck2 build //:git_internal, so Buck-based builds continue using 0.10.9 and do not receive this upgrade, creating a real dependency divergence between Cargo and Buck paths.

Useful? React with 👍 / 👎.

crc32fast = "1.5.0"
ring = "0.17.14"
serde_json = "1.0.149"
Expand Down
Loading