feat: update api version to be 0.12.0 in order to use new Not constraint #2603
Conversation
This file contains 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
Signed-off-by: Tyler Slaton <tyslaton@redhat.com>
tylerslaton
force-pushed
the
update-api-version
branch
from
4135947
to
1be3278
Compare
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ankitathomas, dinhxuanvu, tylerslaton The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
|
/lgtm |
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.
Signed-off-by: Tyler Slaton tyslaton@redhat.com
Description of the change:
Updating the o-f/api version to be 0.12.0 in order to bring in the renaming compound constraint of "None" -> "Not". This also updates the code around that uses the compound constraint API to use Not instead of None.
Motivation for the change:
This is to make the interface for interacting with the negation compound constraint clearer. It also helps to avoid the confusion described in BZ 2034319.
Reviewer Checklist
/doc