docs/api-versioning: Mention changing enum types as an example of an incompatible change#5290
Merged
Conversation
…incompatible change
zebot
added
the
ok-to-test
blackheaven
approved these changes
Jun 25, 2026
supersven
approved these changes
Jun 25, 2026
supersven
left a comment
supersven
left a comment
Contributor
There was a problem hiding this comment.
LGTM 👍
(I'm wondering if we can't have automatized checks for this via swagger / the Servant type ... 🤔 However, this is more a topic for an upcoming Hackathon and not part of this PR's scope)
Member
Author
Wondering the same, we shouldn't wait so long IMO. This can perhaps just be done as BAU work. |
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
4 participants
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.
Checklist
Add a new entry in an appropriate subdirectory ofNo changelog.changelog.d