The June 2026 migration retired the standalone Gazebo repository and moved maintenance of the Gazebo crate family into Buck2:
172703e
The published crates.io metadata has not caught up yet. In particular, gazebo is still 0.8.1 from October 2022 and points to facebookincubator/gazebo, while the maintained in-tree source under facebook/buck2 has continued changing without a version bump. The dupe, cmp_any, display_container, and derive crate pages also still point to the retired repository.
Would you be willing to either:
- Publish patch releases from the Buck2-maintained sources so crates.io carries the current code and repository metadata; or
- Document that downstream consumers should use the Buck2 source directly, including whether future crates.io releases are planned?
This would make the supported dependency boundary clear for downstream Buck2 users and forks without requiring them to infer whether the crates.io artifacts or the in-tree sources are canonical.
Current package page: https://crates.io/crates/gazebo
The June 2026 migration retired the standalone Gazebo repository and moved maintenance of the Gazebo crate family into Buck2:
172703e
The published crates.io metadata has not caught up yet. In particular,
gazebois still0.8.1from October 2022 and points tofacebookincubator/gazebo, while the maintained in-tree source underfacebook/buck2has continued changing without a version bump. Thedupe,cmp_any,display_container, and derive crate pages also still point to the retired repository.Would you be willing to either:
This would make the supported dependency boundary clear for downstream Buck2 users and forks without requiring them to infer whether the crates.io artifacts or the in-tree sources are canonical.
Current package page: https://crates.io/crates/gazebo