Create release workflow#55
Merged
Merged
Conversation
piloulacdog
changed the title
cespio
approved these changes
May 19, 2026
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
2 participants
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.
🚀 Motivation
Releases for this GitHub Action were created manually, which is error-prone and inconsistent. We need an automated workflow to create releases when a new version tag is pushed.
📝 Summary
Added a new
release.ymlworkflow that triggers on semver version tags (e.g.v4.3.0, excluding major aliases). It first runs the existing platform tests and, only if they pass, creates a draft GitHub release with auto-generated release notes.The
test-platforms.ymlworkflow was also updated to:workflow_callso it can be reused by the release workflow