Skip to content

(MOT-4299) refactor: delegate release notifications to Release Control - #727

Draft
ytallo wants to merge 1 commit into
mainfrom
refactor/release-control-notifications
Draft

(MOT-4299) refactor: delegate release notifications to Release Control#727
ytallo wants to merge 1 commit into
mainfrom
refactor/release-control-notifications

Conversation

@ytallo

@ytallo ytallo commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

What changed

  • removes direct Slack calls from Release, Promote Worker, and Repair worker release
  • removes notification status from release and promotion evidence so artifacts contain only release truth
  • retains the legacy --notification-result CLI argument as an ignored compatibility input for reruns of older workflows
  • updates the release SOP to make Release Control the notification owner

Why

Release and promotion are two states of the same deployment. Posting from independent workflows created duplicate root messages and coupled notification mechanics to execution evidence.

Impact

GitHub Actions now executes releases and emits terminal evidence only. The companion Release Control change consumes correlated evidence, maintains one root message per Release run, and keeps history in its thread. Out-of-band runs that are not correlated to a Release Control operation no longer notify Slack.

Companion: iii-hq/release-control#4

Validation

  • focused release_result.py tests
  • Python bytecode compilation
  • YAML parsing for all changed workflows
  • Actionlint for Release, Promote Worker, and Repair worker release
  • git diff --check

Refs MOT-4299

@vercel

vercel Bot commented Aug 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
workers Ready Ready Preview Aug 6, 2026 1:21pm
workers-tech-spec Ready Ready Preview Aug 6, 2026 1:21pm

Request Review

@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: f9c5bfca-7d86-4cc0-8970-8b23ba7376c0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

skill-check — worker

0 verified, 54 skipped (no docs/).

Layer Result
structure
vale
ai
render

Four for four. Nicely done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant