release(sbom): prepare v1.1.0 - #115
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
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.
Release scope
Prepare sbom-diff-and-risk for the �1.1.0 GitHub Release after the merged opaque �om_ref identity fix.
Included:
Design decision
�1.1.0 is a GitHub Release and artifact-provenance release. The existing tag workflow remains the source of truth for the wheel, sdist, checksum manifest, and attestations. Historical v1.0.0 notes remain linked as prior release evidence.
Main risk
Changing the stable pointer and package version can expose stale consumer examples or reviewer contracts. The release-prep tests and route validator pin those surfaces to the same final version.
Compatibility impact
CLI commands and flags remain unchanged. v1.0 report fields and legacy policy files remain readable. Production PyPI publishing remains explicitly deferred and is excluded from this release.
Rollback path
Before tagging, revert commit 4c4f693 or close this draft PR. After tagging, do not move the tag; use a follow-up corrective release and keep the published GitHub Release immutable.
Validation