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
6 changes: 3 additions & 3 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 @@ -53,7 +53,7 @@ sea-orm = { version = "1.1.17", features = ["sqlx-sqlite"] }
flate2 = { version = "1.1.9", features = ["zlib"] }
serde = { version = "1.0.228", features = ["derive"] }
chrono = { version = "0.4.43", features = ["serde"] }
uuid = { version = "1.20.0", features = ["serde", "v4", "v7"] }
uuid = { version = "1.21.0", features = ["serde", "v4", "v7"] }
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 after bumping uuid

Updating uuid in Cargo metadata without the corresponding Buck migration leaves the Buck graph pinned to //third-party/rust/crates/uuid/1.20.0:uuid (see BUCK:68), while Cargo-based jobs use 1.21.0. Because this repo’s CI also runs buck2 build //:git_internal (.github/workflows/base.yml:106), the dependency upgrade is only partial and produces divergent build behavior; the Buck/third-party files should be regenerated and committed with this version bump.

Useful? React with 👍 / 👎.

tokio = { version = "1.49.0", features = ["fs", "io-util"] }
bincode = { version = "2.0.1", features = ["serde"] }
axum = { version = "0.8.8", features = ["macros", "json"] }
Expand Down
Loading