-
Notifications
You must be signed in to change notification settings - Fork 117
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
Re-Tag pre-release correctly on production as latest release #608
Comments
Same issue here, did you find a solution? |
I remember that there was a reason why we couldn't do this in the past, maybe an API was missing or not working correctly. If you could look into it and test if you can mark a pre-release on github as latest, that would be a great start. Once we verified that it's possible, we can work on a pull request to add that functionality |
It looks like this feature is now available in the API. I ran a pre-release then merged to my primary release branch, this removed the pre-release status from the branch. I think this should mean that per the github api, this can now be marked as latest per the
|
Hi!
I'm not sure what the thought process behind the current behaviour is, but for me I'm not sure why a
master
release to an existing pre-release won't mark the release on github as the latest release.Semantic-release for NPM has that behaviour as I would expect.
To clarify what I mean:
next
branchx.x.x@next
NPM packagex.x.x
GitHub release tagged aspre-release
next
branch intomaster
x.x.x@next
NPM package with@latest
But the GitHub release, will NOT be tagged as
latest-release
.I would expect for the GitHub release to also be tagged similar to NPM.
The text was updated successfully, but these errors were encountered: