| Crates.io | burn-central-client |
| lib.rs | burn-central-client |
| version | 0.3.3 |
| created_at | 2025-11-14 18:57:43.468478+00 |
| updated_at | 2026-01-12 19:45:46.943548+00 |
| description | Collection of HTTP calls required to communicate with the backend of burn-central |
| homepage | https://burn.dev |
| repository | https://github.com/tracel-ai/burn-central-client |
| max_upload_size | |
| id | 1933307 |
| size | 86,086 |
Burn Central Client is a Rust crate providing the interface between external tools and the Burn Central server.
It contains all the HTTP calls required to communicate with the backend and acts as the single source of truth for Burn Central’s API definitions.
This crate was extracted from the Burn Central SDK to improve control over versioning and to make breaking changes explicit and easier to manage across projects.
Internal Note
This crate is primarily intended for use by other Burn Central crates (e.g., SDKs, CLIs, and internal services).
It is publicly visible for transparency and automation purposes but is not meant for external integration.
Important
Always stay on the latest major release.
Major versions reflect breaking API changes in the backend, and older versions will stop functioning as server contracts evolve.
This crate follows Semantic Versioning (SemVer):
MAJOR.MINOR.PATCH
Although we aim to minimize breaking changes, the versioning of this crate is tightly coupled with Burn Central’s backend API.
Releases are driven by the server’s route definitions, not by internal library decisions.
Note
We define a breaking change as a change that requires modifying how the code behaves or interacts with the API.
Because of the nature of this crate, many updates will be breaking in the traditional sense — this is acceptable, as the crate is not intended to abstract or stabilize backend definitions beyond their current state.
This is also fine because this crate is not intended for use outside of Tracel-managed projects.
X.0.0)Major releases indicate breaking changes caused by backend modifications.
These should be rare, as the backend typically introduces new route versions (e.g., /v2/...) to preserve compatibility.
If the data model or API contract changes fundamentally and older route definitions must be dropped, a new major version will be published.
0.X.0)Minor releases introduce new functionality, such as additional endpoints or call wrappers.
Existing calls remain fully functional, making these releases non-breaking.
0.0.X)Patch releases include non-breaking adjustments, such as:
All patch updates are backward compatible.
To minimize breaking changes, backend development should follow these principles:
/v2/route) instead of replacing the current version.Crate updates must adhere to the following internal standards:
This crate is maintained by the Burn Central team and should only be modified by internal contributors.
External contributions to this crate will not be accepted.
If you wish to contribute to the CLI or SDK, you are more than welcome to do so.
However, if your change requires updates to this crate, please open an issue in the Tracel repository and request assistance from a team member.