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
Option to Not Set as Latest Release #1339
Comments
To add some color, this is supported by the GitHub Releases API in the form of the |
pull request are welcome :) |
@jetersen cool, part of the reason I opened. I've tried to help on projects before to just get PR's closed. |
here's the pr: #1348 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm dealing with
release/X.Y
branches, each time we have the tool run it increments properly by the filter by commitish feature, however on older versions lets say 1.x vs 2.x, 1.x releases will still get set as "latest". It would be nice to be able to disable this either by branch or by perhaps only allowing latest to be set on tags that are tied back to the primary branch.The text was updated successfully, but these errors were encountered: