Repository navigation
ci: release with mcanouil/release-actions - #182
Merged
Merged
Conversation
The App now pushes the version bump straight to main, so the release is cut on that commit instead of racing an auto-merged pull request. The release body starts with the Unreleased section of the new changelog.
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
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 release workflow now runs on
mcanouil/release-actions@v1instead of its own sed andgh release createsteps.The version scheme stays the same: the date as
YYYY.MM.DD, then-2,-3for further releases on one day, read from the tags.bumprewrites the same two lines ofCITATION.cff, and the patterns are anchored socff-versionnever matches.I replayed the old step and the new one in
ubuntu:24.04for a first, second and third release on one day, andCITATION.cffcame out identical each time.The App is exempt from the ruleset, so it now pushes the bump straight to
main.The bump pull request and its auto-merge are gone, and the release is created on the bump commit.
Before, the release could be created before the merge had landed.
The run refuses an existing tag or release before the push, and it explains how to recover if something fails after the push.
The new
CHANGELOG.mdis now the source of the release body, with the generated notes below it.An empty
## Unreleasedsection stops a release.A later release on the same day gets its count in the title, such as
2026-10-16 (2).The release is still created as the App, so it still starts the image build and the documentation deploy.