-
-
Notifications
You must be signed in to change notification settings - Fork 69
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
use semver 3.0 #464
use semver 3.0 #464
Conversation
@@ -26,7 +26,7 @@ dependencies = [ | |||
"ruamel.yaml >=0.16.10", | |||
"ruamel.yaml.jinja2", | |||
"setuptools >=30.3.0", | |||
"semver~=2.13.0", |
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.
In theory, b/c of this, grayskull should not install semver 3.0.0, right? Anyway, I got it in my env and it broke grayskull. This PR makes it a bit future proof.
sorry for my delay. |
No rush. |
gonna need to add your modifications to my other PR, is that ok? |
@jezdez I cannot merge this one, there is an unrelated problem with a new version of rapidfuzz that is affecting this PR that I would prefer to fix in separated PR. However, I do not have rights to bypass this!? |
@marcelotrevisani the branch protection requires passing the status checks, |
@marcelotrevisani I assumed you'd have access to the branch protection settings given your maintain permissions, but I must have been mistaken about that. |
Should I enable the option to require status checks again? |
Hi @jezdez , I don't have permission to change those options.... |
Latest semver changed this method from
isvalid
tois_valid
.