Repository navigation
fix: align release Doxygen environment - #7
Merged
Merged
Conversation
Contributor
✅MegaLinter analysis: Success
Notices
See detailed reports in MegaLinter artifacts
|
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 post-merge versioning workflow failed after PR #6 because release validation ran on Ubuntu 22.04 with Doxygen 1.9.1, while the green pull-request integration job ran on Ubuntu 24.04 with Doxygen 1.9.8. The release candidate itself passed all source and distribution regression cases; the failure occurred only at the XML-shape assertion for the governed
Yieldsparagraph.This PR removes that environment drift by pinning both the test workflow and the versioning workflow to
ubuntu-24.04. That keeps release validation aligned with the environment in which the Doxygen structural assertions are proven, and avoids relying on the movingubuntu-latestalias.This change deliberately does not weaken the XML assertions or alter filter behavior.
One separate release-process issue remains: the versioning workflow creates the semver tag before validation, so
v0.2.0was created even though the release job later failed. This PR does not delete or move that tag.