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
{{ message }}
Repository navigation
Add an option to not mark maintenance releases as latest #817
I would like to have an option to not mark maintenance releases as latest on github.
Currently our main branch is on v4 and we've maintenance releases on v2.
Everytime a v2 get's released, it's marked as latest by default.
So an option to override would be very useful.
changed the title [-]Add an option to not mark maintenance releases as latest[/-][+]Add an option to `not` mark maintenance releases as latest[/+]on Apr 22, 2024
Activity
[-]Add an option to not mark maintenance releases as latest[/-][+]Add an option to `not` mark maintenance releases as latest[/+]gr2m commentedon Apr 25, 2024
Hmm sounds like a bug to me in the first place. We probably just didn't get around to address this, or the APIs didn't exist at the time.
travi commentedon Apr 25, 2024
agreed. i cant think of a reason why a maintenance release should ever be marked as latest
michaelchambaud-eaton commentedon Jul 24, 2024
I have the same issue.
There is a
make_latest: string(defaults: true) in GH API -> https://github.com/proxy/docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#create-a-releaseI'm thinking it should be added here:
github/lib/publish.js
Line 54 in c70cfbf
travi commentedon Jul 24, 2024
We do want to fix this. If you've investigated far enough to see a solution, please feel free to send a PR to keep this moving forward
robfraz commentedon Nov 13, 2024
Hello - is there any news on this issue? It looks like the linked PR has stalled...? 😢
Is there any kind of workaround anyone can recommend?
viceice commentedon Mar 1, 2025
simply setting
make_latest=legacywill probably fix it too?scriptcoded commentedon Aug 2, 2025
I "fixed" this in my own repo by adding this step after running the release (GitHub Actions).
github-actions commentedon Feb 7, 2026
🎉 This issue has been resolved in version 12.0.5 🎉
The release is available on:
Your semantic-release bot 📦🚀
viceice commentedon Feb 11, 2026
not fixed
viceice commentedon Feb 11, 2026
the new check seems not enough, we use this
branchesconfig:{ "branches": [ { "name": "maint/+([0-9])?(.{+([0-9]),x}).x", "range": "${name.replace(/^maint\\//g, '')}" }, "main" ] }https://github.com/containerbase/base/blob/main/.releaserc.json
viceice commentedon Feb 11, 2026
please reopen, the
make_latestalso needs to be added here:github/lib/publish.js
Lines 165 to 170 in f367e3a
viceice commentedon Feb 11, 2026
https://github.com/proxy/docs.github.com/en/rest/releases/releases?apiVersion=2022-11-28#update-a-release
the patch is setting
make_latestagain to true by default. that only happens when publishing assets.github-actions commentedon Feb 12, 2026
🎉 This issue has been resolved in version 12.0.6 🎉
The release is available on:
Your semantic-release bot 📦🚀