ci: Add some automation for making releases #969
Merged
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.
With this PR, there's one action that runs on any PR that targets branches
releases
orrelease/*
, and will make a trial run of the changelog generation and version bumping. This only works on PRs on the main repo, for permission reasons.A second action will automatically run on branches
releases
orrelease/*
, generate the changelog, execute the version bump, and finally create a GitHub release with the generated changelog and version number. This release can be manually published, and when that happens, a git tag is created on the bump commit.I've tested all this over on https://github.com/paulgessinger/release-test but I don't think it's bulletproof. I'd like to run this for a bit and see if it does the job. There is the possibility for manual intervention before anything (kind of) irreversible happens, so that should be fine.