-
Notifications
You must be signed in to change notification settings - Fork 0
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
Smarter patches #2
Labels
bug
Something isn't working
Comments
Actually I think we do. This will be fixed by changing the predicates that dictates whether to do the whole "post-version" thing from "is a patch version" to "the post-version does not already exist". This should work for both the normal case and the |
Geogi
added
bug
Something isn't working
and removed
enhancement
New feature or request
labels
May 11, 2020
Re-tagging as a bug. I got confused but the solution above is the expected behavior in my opinion. Will fix now. |
Confirmed fixed by #3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now pushing a patch reverts the
-dev
prefix, which is bad (see wiki). This was made because of possible interactions with--for
(i.e. pushing a v1.0.1 when v1.1 exists should not create a v1.1-dev) but even beyond that some thinking may be necessary.Should patch releases go to a different branch ? We probably don't want to see the manifest in master do this :
The text was updated successfully, but these errors were encountered: