Spec versions
A project keeps every spec you import. The Specs page lists them all and lets you choose which one is current, label them, and mark where each one is in its life.
Spec history
Each row shows the spec's version, label, lifecycle, status, endpoint count, when it was ingested and where it came from.
To add one, press Upload new spec. You can leave the page while it processes: generation continues in the background.
The current version
One version is Current: it is what your docs, SDKs and MCP server build from. Press Make current on another row to switch.
To let readers switch between several published versions of your docs, see versioning.
Lifecycle
Mark a version so readers know what they are looking at.
| Lifecycle | Meaning |
|---|---|
| Stable | Safe to build on |
| Beta | Still changing |
| Deprecated | Still works, but being retired |
A version can also carry a lifecycle note in your own words, and a sunset date, the date it stops working.
Removing a version
Choose Delete spec version to remove one from the list.
What changes between versions
Octri compares each new version with the one before it and writes a changelog, marking breaking changes. Your SDK's version number comes from info.version in the spec, as SDK versioning explains.
From the CLI
octri specs list lists your spec versions, and octri docs versions chooses which are published.