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
At the moment, if you (for example) release v6.0.0b1 then v6.0.0, you have to delete the v6.0.0b1 release first or v6.0.0 won't include all the relevant changes from the last stable version.
If GithubApi.last_release were to ignore prereleases (TODO: determine technical requirements for this), it would avoid this problem entirely. It might be worth renaming it to make it clear it doesn't include prereleases (maybe to last_stable_release?), but I'm not sure it matters as long as it's documented.
The text was updated successfully, but these errors were encountered:
At the moment, if you (for example) release
v6.0.0b1
thenv6.0.0
, you have to delete thev6.0.0b1
release first orv6.0.0
won't include all the relevant changes from the last stable version.If
GithubApi.last_release
were to ignore prereleases (TODO: determine technical requirements for this), it would avoid this problem entirely. It might be worth renaming it to make it clear it doesn't include prereleases (maybe tolast_stable_release
?), but I'm not sure it matters as long as it's documented.The text was updated successfully, but these errors were encountered: