You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
To add some color, this is supported by the GitHub Releases API in the form of the make_latest param. The release-drafter would need to be updated to allow us to set that param as an input and pass it through on the calls to GitHub.
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: