API lifecycle management - #5
Merged
Merged
Conversation
DawMatt
commented
Jul 5, 2026
Owner
- Add multiple major versions of the same API into Backstage at the same time, to represent multiple versions running in production in parallel
- Demonstrate how the multiple API versions would all be searchable and accessible, but the most recent version would be prominent and the only one offered to a new user looking for this type of API.
- Show how we would represent APIs progressing through the main lifecycle: development, test, production. Including how these lifecycle states can vary across each API version.
- Show how we manage API retirement. Including marking APIs for deprecation and then retiring them.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.