feat(APP-820): frontend release Slack improvements#1177
Merged
tyhonchik merged 1 commit intoJun 12, 2026
Conversation
|
🚀 Preview Deployment: View Here |
|
E2E results (preview) Smoke
|
- @-mention the code-owner team in the release-start head message (op://kv_app_infra/SLACK_CODEOWNERS_GROUP_ID — same key as backend, app vault) - reflect lifecycle status IN the head message via chat.update: Started -> Cancelled / Completed (production). slack-notify action+script gain an optional update_ts (chat.update) input; cancel/prod re-read the changelog from the PR/release body so the rich head is preserved while status flips - add a production-only CI Gate notify-gate job mirroring backend (runs parallel to deploy, posts team ping + run link into the release thread). The actual pause is the production Environment Required-reviewers rule (configure in repo Settings -> Environments -> production)
tyhonchik
force-pushed
the
app-820-cleanup-be-release-workflows-and-improve-fe-release
branch
from
fea5a5b to
0849f5d
Compare
milosh86
approved these changes
Jun 11, 2026
tyhonchik
deleted the
app-820-cleanup-be-release-workflows-and-improve-fe-release
branch
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
2 participants
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.
Improvements to the frontend release Slack notifications, mirroring the backend flow.
Changes
app-release-v2.yml) now pings the code-owner team viaop://kv_app_infra/SLACK_CODEOWNERS_GROUP_ID(same key as backend, app vault).chat.update) to show Started → Cancelled / Completed (production), instead of status living only in thread replies:slack-notifyaction +slackNotify.jsgain an optionalupdate_tsinput (chat.update path).release-pr-cancel.yml) and on prod success (app-production.yml) the changelog is re-read from the PR/release body (slack_ts marker stripped) so the rich head is preserved while only the status flips.notify-gatejob inapp-production.yml, running parallel todeploy(never blocks it), posting a "Waiting CI Gate" ping with the team mention + run link into the release thread, mirroring backend.