Revisions are like a Git Commit to persist your daily work on the API
specification. The revision log keeps track of all your changes over time.
As soon as your API specification is ready to launch, create a release.
Each release then passes through the API lifecycle, starting with the date
of publication, through a “deprecated” state to the "end of life".
API changelog
Revisions
Revisions support you in your daily work on your APIs. A revision is like
a Git Commit. It helpts you to keep track of all your changes over time.
You can create unlimited revisions from any API. Via a build in changelog
you can identity API changes. And faulty revisions can easily be deleted
again.
Managing API Versions
Releases
You can manage your API Versions with API Releases. For each API you can create unlimited
API Releases. When creating a new Release you have to select the revision the Release
should be based on, provide a version number, and select the API resources (endpoints)
which should be included. Everything else like models (schemas), parameters and authentication
is automatically calculated by APITree. After creation the Release enters the state
Unreleased and is only visible to use / within your organization. Click
on Release to share it with others.
Note: It is possible to create API Shares for Unreleased Releases.
