Notify on merge queue failures#581
Open
bschwedler wants to merge 2 commits into
Open
Conversation
The action previously skipped silently when no previous workflow runs were found on main. This prevented merge queue failures from triggering notifications, since merge queue runs land on ephemeral refs and never appear in a main-branch run query. Now: no history + failed → fire failure notification; no history + passed → skip. State-transition logic is unchanged for builds with history.
Extend `bakery ci matrix` with a `--latest` flag that mirrors the flag already on `bakery build`. For regular versions it keeps only those with `latest: true`; for matrix images it keeps only the highest-version combination (the row where `ImageVersion.latest` is set by `_matches_latest`). Add a `latest-only` boolean input to `bakery-build-pr.yml` that passes `--latest` to the matrix generation steps, so calling workflows can opt individual event types into a faster subset run. Add a `multiversion` test context and BDD scenarios that verify the flag filters non-latest versions from the output.
bschwedler
commented
Jun 9, 2026
| run: | | ||
| FULL_MATRIX=$(bakery ci matrix --quiet --dev-versions "$DEV_VERSIONS" --matrix-versions "$MATRIX_VERSIONS" --context "$BAKERY_CONTEXT" | jq --compact-output .) | ||
| LATEST_FLAGS=() | ||
| if [ "$LATEST_ONLY" = "true" ]; then LATEST_FLAGS=(--latest); fi |
Contributor
Author
There was a problem hiding this comment.
I want to be able to run only the latest version of every image for each PR.
This allows us to enable merge queues in all the repos. Then when ready to merge it runs the full suite without passing --latest.
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 Slack notification action previously skipped silently when no prior
run history was found. Merge queue runs on ephemeral refs never appear
in a main-branch run query, so that guard was swallowing all merge queue
failures with no notification.
Now: no history + passing → still skip. No history + failing → notify.