Repository navigation
Conversation
The repository had no release automation. Tags had to be created and pushed by hand, and the release notes written in the GitHub UI. Nothing verified that a version number was well-formed or that it had not been released before, and the contents of the notes depended on whoever happened to cut the release. The new workflow runs on demand from the Actions tab and takes the version number as its only input. It rejects a malformed number and one that is already tagged, refuses to run outside main, collects the commits since the previous release into Features, Bugfixes and Tasks sections, creates the tag and publishes the GitHub Release. A version with a suffix such as 4.1.0-beta.1 is published as a prerelease and does not replace the current stable release. Stable releases list everything since the last stable one, including what already shipped in intermediate betas, while each beta lists only its own changes. Tag names carry no leading "v". The old v3.0.0 and v3.0.1 tags stay as they are, but every new release uses the plain number and so matches the 1.0.x, 2.0.0 and 4.0.0 tags.
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 repository had no release automation. Tags had to be created and pushed by hand, and the release notes written in the GitHub UI. Nothing verified that a version number was well-formed or that it had not been released before, and the contents of the notes depended on whoever happened to cut the release.
The new workflow runs on demand from the Actions tab and takes the version number as its only input. It rejects a malformed number and one that is already tagged, refuses to run outside main, collects the commits since the previous release into Features, Bugfixes and Tasks sections, creates the tag and publishes the GitHub Release. A version with a suffix such as 4.1.0-beta.1 is published as a prerelease and does not replace the current stable release. Stable releases list everything since the last stable one, including what already shipped in intermediate betas, while each beta lists only its own changes.
Tag names carry no leading "v". The old v3.0.0 and v3.0.1 tags stay as they are, but every new release uses the plain number and so matches the 1.0.x, 2.0.0 and 4.0.0 tags.