-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for version number validation against mixins #3215
Support for version number validation against mixins #3215
Conversation
Signed-off-by: David Gannon <19214156+dgannon991@users.noreply.github.com>
@dgannon991 Yes the format looks like what I thought about. Didn't really think about adding the full semver constraint, but I think it makes sense, and it would allow to later implement logic that could automatically download the right version if needed |
Nice. I’ll try and get the other half of it down for Thursday. Cheers! |
Signed-off-by: David Gannon <19214156+dgannon991@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks really good, added a few small comments
Signed-off-by: David Gannon <19214156+dgannon991@users.noreply.github.com>
What does this change
Added a check on version numbers if specified in your porter YAML
What issue does it fix
Delivers towards #3136
Notes for the reviewer
@kichristensen - this is just a draft to make sure I'd got the right idea, before adding the checks into the linting side. I was fairly sure I'd understood, but thought it was worth double checking as it's been a little while :)