Repository navigation
build: prepare DDK release 19.2.0 - #1533
Merged
Merged
Conversation
The release workflow requires every feature.xml to declare the release version: `.github/workflows/release.yml` fails create_tag unless each one reads `<release>.qualifier`. The v19.2.0 dispatch failed because the two features had drifted apart and neither matched: com.avaloq.tools.ddk.feature 19.1.2.qualifier com.avaloq.tools.ddk.runtime.feature 19.1.1.qualifier They diverged because individual PRs bump a feature whenever a bundle it contains changes, to satisfy Tycho's baseline gate. That is per-change versioning; the release expects the two features to move in lockstep to the release version, which is what the "prepare DDK release" commit does. Set both features and their poms to 19.2.0, and update the two ddk-repository/category.xml pins (url and version) to match. Same five files and same shape as c6e5684 (release 19.1.0). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
joaodinissf
enabled auto-merge (rebase)
September 8, 2026 11:48
rubenporras
approved these changes
Sep 8, 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.
Problem
The
v19.2.0release dispatch failed atcreate_tag. The release workflow requires everyfeature.xmlto declare the release version —release.yml:87-104fails unless each one reads<release>.qualifier:The two features had drifted apart, and neither matched the release version.
Why they drifted
Individual PRs bump a feature whenever a bundle it contains changes, because Tycho's
compare-version-with-baselinesfails on unchanged versions with changed content. That is per-change versioning, and the two features accumulate bumps at different rates depending on which bundles a PR touches — hence 19.1.2 versus 19.1.1.The release expects something different: both features at the release version, in lockstep. That reconciliation is what a
build: prepare DDK release …commit does.Fix
Set both features and their poms to
19.2.0, and update the twoddk-repository/category.xmlpins (urlandversion) to match. Same five files and the same shape asc6e568436(release 19.1.0).Verification
feature.xml: both now report19.2.0.qualifier, gate passes. (Note the workflow'sawkuses GNU three-argumentmatch(), so it only runs under gawk on the CI image, not BSD awk on macOS.)clean verify checkstyle:check pmd:pmd pmd:cpd pmd:check pmd:cpd-check spotbugs:check.Follow-up worth considering
This reconciliation will be needed before every release as long as per-PR feature bumps continue. Either the release gate accepts a version at or above the release version, or feature bumps are deferred to release-prep only. Out of scope here.
🤖 Generated with Claude Code