ci: prune old release pages after a release - #3
Merged
Merged
Conversation
The releases page is for finding the current version; CHANGELOG.md is the ledger, and semantic-release writes the same notes into both. Keeping every release forever only makes the page harder to read. Every major stays, along with the last two feature releases and the last three fixes. Tags are never touched — Packagist resolves a version from the tag, and a lock file naming one has to stay installable years later, so `gh release delete` is deliberately called without --cleanup-tag.
|
🎉 This PR is included in version 1.0.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The releases page is for finding the current version;
CHANGELOG.mdis the ledger, and semantic-release writes the same notes into both. Keeping every release forever only makes the page harder to read.Kept: every major, the last two feature releases, the last three fixes — plus whatever GitHub is currently showing as latest, whichever bucket that fell into.
Tags are never touched
This is the whole risk of the change, so it is worth being explicit. Packagist resolves a version from the git tag, not from the GitHub release, and a
composer.locknaming a version has to stay installable years from now.gh release deleteleaves the tag alone unless asked for--cleanup-tag, which this deliberately never passes.So the only thing removed is the rendered page. Nothing about installing an old version changes, and no notes are lost.
🤖 Generated with Claude Code