First Api compatibility tests#306
Closed
majst01 wants to merge 1 commit into
Closed
Conversation
majst01
force-pushed
the
api-compatibility-tests
branch
3 times, most recently
from
231a33a to
9c92b15
Compare
majst01
force-pushed
the
api-compatibility-tests
branch
from
9c92b15 to
062a18f
Compare
Contributor
Author
|
closed in favour of metal-stack/releases#298 |
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
1 participant
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.
Description
Create a test which tests the api compatibility between v1 and v2.
already found one BUG in metal-apiserver with this: metal-stack/metal-apiserver#219
Used AI-Tools ✨