Skip to content
Closed
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
7 changes: 5 additions & 2 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 @@ -43,7 +43,7 @@ tokio-stream = "0.1.18"
natord = "1.0.9"
tempfile = "3.27.0"
path-absolutize = "3.1.1"
similar = "2.7.0"
similar = "3.1.1"

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 Regenerate Buck metadata for the bumped crate

Because this repo's PR workflow runs buck2 build //:git_internal for Cargo.toml changes, the dependency bump needs the generated Buck files updated as well. I checked the Buck wiring: BUCK still depends on //third-party/rust/crates/similar/2.7.0:similar, third-party/rust/crates/similar/2.7.0/BUCK still fetches the 2.7.0 crate, and buckal.snap still records similar@2.7.0, so Buck-built artifacts will continue to use 2.7.0 while Cargo uses 3.1.1. That can let Cargo tests pass while the canonical Buck build/prod path misses the new dependency version or later fails when code relies on 3.x APIs; please run the documented cargo buckal migrate and commit the generated updates.

Useful? React with 👍 / 👎.

sha2 = "0.10.9"
crc32fast = "1.5.0"
ring = "0.17.14"
Expand Down
Loading