feat(kit): alert to Slack from CI runs + bump the driver-agents pin (v1.7.0) - #22
Conversation
…v1.7.0) Kit-only release — the five reusables are untouched, so the caller stubs keep pinning v1.6.0's 0a3934f and no stub-repin wave is needed. - claude.yml + shopify-tool-smoke.yml: DRIVER_AGENTS_REF -> 0404c4e (driver-agents main @ 2026-07-31), picking up the human-readable Slack alert wording. Pins move in lockstep, per the house rule. - Both provisioning steps now write the org-level SHOPIFY_ALERT_WEBHOOK secret to the runner and export SHOPIFY_ALERT_WEBHOOK_FILE + SHOPIFY_ALERT_HOST_LABEL, so the admin tool's destructive/failed-call alerts post to #driver-agents-status from Actions runs like they do from the box. The host label is the run URL — the runner's audit log doesn't outlive the job, so the alert points at the run instead. Absent secret = alerts silently off, nothing else changes. - READMEs: v1.7.0 notes + org-secret documentation.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
WalkthroughThe v1.7.0 kit-only release updates the pinned ChangesShopify alert provisioning
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Kit-only release: the five reusables are untouched, so the caller stubs keep pinning v1.6.0's
0a3934f— no stub-repin wave needed. The fleet wave re-copies only the two kit files below.What changed
DRIVER_AGENTS_REF→0404c4e(driver-agents main @ 2026-07-31) in bothclaude.ymlandshopify-tool-smoke.yml(lockstep rule) — picks up the human-readable Slack alert wording from driver-agents PR v1.0.2 — batched refinements (start: PR-first marker wording) #2.SHOPIFY_ALERT_WEBHOOKsecret (the#driver-agents-statusincoming webhook, already created org-wide with visibilityall) to the runner's throwaway disk and exportSHOPIFY_ALERT_WEBHOOK_FILE+SHOPIFY_ALERT_HOST_LABEL, so the admin tool's destructive/failed-call alerts fire from Actions runs exactly as they do from the box. The host label is the run URL — the runner's audit log doesn't outlive the job, so the alert points the reader at the run log instead. Absent secret = alerts silently off; nothing else changes (the tool's own best-effort posture).v1.7.0section + org-secret documentation in the kit README.Verification
actionlint(with shellcheck over therun:blocks) passes locally on both changed workflows.admin-graphql.shat the new pin (SHOPIFY_ALERT_WEBHOOK_FILE,SHOPIFY_ALERT_HOST_LABEL— both read by the tool; label override exists precisely for non-box emitters).Summary by CodeRabbit
New Features
Documentation