Repository navigation
Fix release version validation and CI SBOM uploads - #2
Merged
Merged
Conversation
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
1 participant
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 v0.2.1 tag points to unchanged v0.2.0 source, so container publication fails its version check. Tag CI also attempts to attach its SBOM to the GitHub release with a read-only token.
Prepare v0.2.2 without moving the existing published tags, keep the CI SBOM as a workflow artifact, and validate the package, runtime and release-tag versions with explicit diagnostics. Container publication retains its signed-tag requirement and SBOM/provenance attestations. Document the release procedure and the failed v0.2.1 publication.
Validation: 58 local tests passed; Ruff, actionlint and git diff checks passed. The version checker accepts v0.2.2 and rejects v0.2.1.