-
Notifications
You must be signed in to change notification settings - Fork 47
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
should reject x.y.(z+1) if x.y.z has not been merged #225
Comments
This is... partially fixed by automerge? Automerge only merges if the version bump is one of the following:
So it doesn’t fully solve the problem. But certainly we don’t automerge PR’s that don’t follow those rules. |
Yes, definitely helps but registration should not be allowed in the first place. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
People keep opening flights of PRs to register versions 0.1.2, 0.1.3, 0.1.4 and 0.1.5—all before 0.1.2 has been merged. Registrator should reject such attempts and direct the package author to update 0.1.2 instead. Similarly, if there's a PR to register a package with one version number, say 0.1.0, if the author tries to register the same package with a different version number, say 1.0.0, Registrator should refuse and instruct the author to update the original PR.
The text was updated successfully, but these errors were encountered: