Repository navigation
Conversation
… on main The dogfood image publish failed on main on 2026-11-02 and 2026-11-03 without anyone noticing, so workspaces kept pulling the 2026-10-27 image. Post the same failure alert as ci.yaml and nightly-gauntlet.yaml.
This branch has not been deployed
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.
The dogfood image workflow had no failure alert. Its runs on main on 2026-11-02 and 2026-11-03 both failed on network errors and weren't re-run, so workspaces kept pulling the 2026-10-27 image until a manual re-run on 2026-11-03.
This adds the
notify-slack-on-failurejob fromci.yamlandnightly-gauntlet.yamlwith its own header. It posts to the sameCI_FAILURE_SLACK_WEBHOOKand mentions the same bot withBLINK_CI_FAILURE_PROMPT, as the nightly gauntlet already does. It runs only on main, the only ref that pushes the image.Decision log
BLINK_CI_FAILURE_PROMPT(the API returns 403), so I don't know its wording. The nightly gauntlet reuses it for a non-CI failure, so this follows that.permissions: {}: the job only calls a webhook, so it gets no token permissions instead of inheriting the workflow'scontents: read.curlstubbed, and it parses as JSON, including a prompt with quotes.make pre-commit-light(what the hook runs for this change, with actionlint) passes, and zizmor 1.11.0 with the Makefile's flags reports no findings (run inubuntu:26.04, because the local binary needs a newer glibc).