Repository navigation
Conversation
publish.yml: security fixes for explicit tags, artifact hand-off and OCI checks
DeviaVir
enabled auto-merge (squash)
October 30, 2026 12:23
DeviaVir
disabled auto-merge
October 30, 2026 12:23
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 #4 and #6 to
v1. After the merge, this will be taggedv1.1.0. No tag points to the earlierv1head with #4 alone.Security fixes (#6) for the code that is now on
v1:prod-or have the derived<hex>-<number>form.publishsigns only an image whose blobs are all in the build artifact, and rejects ambiguous OCI JSON.build-environmentmust differ fromenvironment.Existing callers are not affected: none sets
tags,platformsorbuild-environment.Who this ships to: consumers that trust
refs/heads/v1pick this up on the merge.