Repository navigation
ci: fix main push workflow validation - #475
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.
Summary
Fix the three multiline POSIX
[provenance tests inbuild.yaml. Bash accepted the old form during syntax-only validation but the trustedmainpush run failed at runtime with[: missing \]'`, leaving the metadata and aggregate build checks red. The comparisons are unchanged; only their shell command shape is corrected.This is a follow-up to #474, which landed the main-controlled workflow and v3 policy. It does not modify
v3or use #473 as a vehicle.Validation
.github/workflows/build.yamland passed every embeddedrunscript throughbash -n.pushandpull_request_targetenvironments; both reached and passed immutable OID/provenance validation.git diff --checkpassed.Security and trust boundaries
The fix does not change workflow refs, immutable OID checks, local-only Nix/fixture/hardware behavior, BuildBuddy target selection, credential descriptor handling, or the push-only credential gate. PR workflows remain credential-free and main-controlled.