feat: add semver gte, lte and cidr matching constraint#115
Merged
Conversation
gastonfournier
approved these changes
Mar 13, 2026
Contributor
gastonfournier
left a comment
There was a problem hiding this comment.
LG, but do we need IPV6 specs? I'd say yes, whether they work or not I think it's better to have them speced out
Member
Author
Hmm. Good point let me add them quickly and validate against Ygg |
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.
Adds Semver GTE, Semver LTE and CIDR matching constraints. The CIDR matching constraints are modeled on the same behavior as the IPAddress Strategy - they're intended as a drop in replacement for that strategy. Tired of having conversations around what it would take to deprecate that strategy, we're just doing it now