Versioning & deprecations
What the beta means before 1.0, how Graphon versions the API, and how it announces deprecations.
Beta
The Graphon API is in beta until version 1.0. The beta covers the Graphon API, the storage API, the MCP tools, and the CLI. Before 1.0, a release can make a small breaking change, such as a renamed field or a new error code. The changelog lists each breaking change with how to update your code. A larger breaking change gets a deprecation first.
Code and agents read the same list with GET /v1/changelog, the list_changelog MCP tool, or graphon changelog. Every API response carries x-graphon-last-breaking-change, the date of the newest breaking change.
API version
The API version is in the path, for example /v1. From 1.0, a version stays stable for its lifetime, and a new major version uses a new prefix.
Deprecations
When an operation is going away, Graphon states it on the operation page and in the changelog. A deprecation names:
- The replacement operation, or why the capability is gone.
- A calendar end-of-life date, not "soon".
While the old call still works, the same note appears on its reference page. See the changelog for the dated list.