ci: pass release version to Ketryx on release/v* branches#562
Merged
Conversation
olivermeyer
requested review from
a team and
helmut-hoffer-von-ankershoffen
as code owners
olivermeyer
added
skip:test:long_running
When CI/CD runs on a release/v* branch, extract the semver from the branch name and pass it as the Ketryx `version` input instead of `commit-sha`. This associates the build with the correct Ketryx release entry rather than a transient commit SHA, enabling proper compliance approval collection during the prepare-release phase. On all other contexts (PRs, main, tags), the existing commit-sha behaviour is unchanged. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
olivermeyer
force-pushed
the
fix/ketryx-version
branch
from
9db7917 to
cc50636
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the CI/CD workflows so that runs on release/v* branches can report a stable release version to Ketryx (instead of a commit SHA), and ensures PRs targeting release branches trigger the full pipeline.
Changes:
- Extend
pull_requesttriggers to includerelease/v*base branches. - Extract a
release_versionfrom the branch name and forward it into the Ketryx reporting workflow. - Add an optional
versioninput to the reusable Ketryx workflow and conditionally prefer it overcommit-sha.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| .github/workflows/ci-cd.yml | Adds PR trigger for release/v* and computes/forwards release_version to Ketryx reporting. |
| .github/workflows/_ketryx_report_and_check.yml | Adds version input and updates Ketryx action invocation to prefer version over commit-sha. |
|
arne-aignx
approved these changes
Apr 24, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. |
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.
Why?
When CI runs on a
release/v*branch, Ketryx should associate the build with the named release version (e.g.1.2.3) rather than a transient commit SHA, so that compliance approvals collected during the prepare-release phase are correctly linked. PRs targeting release branches should also trigger the full CI/CD pipeline.How?
The
get-commit-messagejob now extracts the semver from the branch name and exposes it asrelease_version. This is forwarded to_ketryx_report_and_check.ymlas a new optionalversioninput; when set, it is passed to the Ketryx action andcommit-shais omitted. On all other contexts (PRs to main, main pushes, tags) the existing commit-SHA behaviour is unchanged. Thepull_requesttrigger is also extended to includerelease/v*base branches.