Distillation

Date: Sep 8, 2026

• 🟡 (17:52) [scheduled follow-up] User requested checking the Craft release-branch image workflow, publish request #9454 fresh CI labels, and Craft 2.31.0 release status; instructed not to bypass publish gating.
• 🟡 (17:52) Publish workflow run 34259475611 completed with conclusion failure; Publish a new version job 102173522513 ran from 17:50:21Z to 17:51:55Z.
• 🟡 (17:52) In job 102173522513, steps 1–10 succeeded: Set up job; Pull getsentry/craft:latest; Get repo contents; Setup Node; Install yarn dependencies; Parse and set inputs; Resolve CI-approved release revision; Inform start; Get Release Bot auth token; and Check out target repo.
• 🟡 (17:52) In job 102173522513, Resolve publish location (step 11, 17:51:48Z–17:51:49Z) failed; downstream Set targets (step 12) and Publish using Craft (step 13) also failed, so Craft itself did not run.
• 🟡 (17:52) In job 102173522513, Update completed targets and remove label (step 14) and Inform about failure (step 16) succeeded; Inform about cancellation (step 15) and Close on success (step 17) were skipped. Cleanup Post Check out target repo (31), Post Get Release Bot auth token (32), Post Get repo contents (34), and Complete job (35) succeeded; Post Setup Node (33) was skipped.
• 🟡 (17:52) Waiting for CI job 102173523706 was completed/skipped, with no steps, at 17:50:16Z.
• 🟡 (17:52) Publish issue https://github.com/getsentry/publish/issues/9454 remained open and had only the ci-ready label; the prior accepted label was no longer present.
• 🟡 (17:52) Issue #9454 comments recorded: approval and automatic CI checking at 17:45:44Z; CI passed for getsentry/craft@2.31.0 and publishing began at 17:50:15Z; workflow run 34259475611 was announced at 17:51:45Z; and failure was reported at 17:51:51Z with a suggestion to delete the 2.31.0 branch and start over if it was a bad branch.
• 🟡 (17:52) Craft 2.31.0 release artifact was not found; the release was not published.
• 🟡 (17:52) Assistant concluded publication failed before Craft ran at Resolve publish location, and stated it would inspect the failed step and fix the controller path rather than bypass publish gating.