syntaqxThe g1t CLI prints JSON with each object's keys in sorted order however it is built, and its table of API operations lists each body's fields in sorted order. Another crate in the workspace turns on serde_json's preserve_order, and a shared build carried it into the CLI, so --json output and the generated table changed order depending on what was built alongside it, and cargo test across the workspace failed. The table is regenerated for the API after open sign-ups, which no longer has the personal invite operations.e6ce8e8History
- ..
- advisories.rs
- code_scanning.rs
- config.rs
- deps.rs
- fixes.rs
- history.rs
- lib.rs
- manifests.rs
- overview.rs
- patterns.rs
- planning.rs
- pull_text.rs
- ranges.rs
- registries.rs
- resolved.rs
- schedule.rs
- secret_alerts.rs
- security_updates.rs
- store.rs
- suite.rs
- suite_store.rs
- summaries.rs
- supply_chain.rs
- timezones.rs
- update_store.rs
- updates.rs
- version_updates.rs
- yaml.rs