ci: add workflow_dispatch + dry_run support to release workflow - #331
Merged
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
umaucher
force-pushed
the
um_release_workflow
branch
from
July 9, 2026 12:18
9504d30 to
ea5a959
Compare
umaucher
marked this pull request as ready for review
July 9, 2026 13:34
umaucher
requested review from
PandaeDo,
antonkri and
vinodreddy-g
as code owners
July 9, 2026 13:34
Contributor
Author
|
dry-run for v0.3.3 see https://github.com/umaucher/persistency/actions/runs/29021445771 |
antonkri
approved these changes
Jul 10, 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
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.
What
Adds
workflow_dispatchtrigger with adry_runflag to the release workflow, and restructures it into two jobs.Why
Before creating a real release tag it must be possible to validate the full build/test/coverage pipeline without side effects. Previously the workflow only triggered on
release: created, making it impossible to test without creating an actual GitHub release.Changes
workflow_dispatchtrigger withversion(X.Y.Z) anddry_run(default:true) inputsprepare-releasejob (skipped on dry run): bumpsMODULE.bazel, commits, creates tag + GitHub releaserelease-verificationjob: runs build → unit tests → Rust coverage → C++ coverage → uploads ZIP artifact; attaches to release only when not a dry runsetup-bazel@0.15.0→@0.18.0(canonical version in cicd-workflows)upload-artifact@v4→@v6(canonical version in cicd-workflows)release: createdtrigger for backward compatibilityTesting
Dry run can be triggered from this branch without merging: