fix: generate correct provenance on non-default branches#1637
Merged
RoyalOughtness merged 1 commit intosecureblue:livefrom Nov 30, 2025
Merged
fix: generate correct provenance on non-default branches#1637RoyalOughtness merged 1 commit intosecureblue:livefrom
RoyalOughtness merged 1 commit intosecureblue:livefrom
Conversation
The generated provenance should only be for the `latest` tag on the default branch; otherwise, the tag has a form generated from the branch name or PR number and the OS major version number. Also simplified the base image verification steps in the build workflows so they don't rely on assumptions about secureblue image naming conventions.
RoyalOughtness
approved these changes
Nov 29, 2025
EsseLowNitro
approved these changes
Nov 30, 2025
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
3 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.
The generated provenance should only be for the
latesttag on the default branch; otherwise, the tag has a form generated from the branch name or PR number and the OS major version number.Also simplified the base image verification steps in the build workflows so they don't rely on assumptions about secureblue image naming conventions.