Repository navigation
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
There was a problem hiding this comment.
CodeQL found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.
tyhonchik
force-pushed
the
app-1066-release-ceremony
branch
from
October 12, 2026 16:16
2444027 to
f564396
Compare
Contributor
Author
|
CodeQL flags |
…ar mirror Every consumer release now reads the same in Slack: notify.yml owns the texts (start, gate with the team ping, result, tests, failure), deploy-vercel/deploy-docker/e2e post through it, release-pr-cancel and release-complete flip the head message, every workflow tells the thread when it fails. release-start mirrors the release into a Linear pipeline. deploy-vercel gains build-only secrets and the output guard, deploy-docker a prepare-command.
tyhonchik
force-pushed
the
app-1066-release-ceremony
branch
from
October 12, 2026 16:41
f564396 to
9557cff
Compare
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.
Every consumer release reads the same in Slack, from one place:
notify.ymlowns the ceremony texts (start,gatewith the team ping,result,tests,failure,message) and finds the release thread from a ts, a PR number or a release tag (steps/resolve-slack-thread).deploy-vercel,deploy-dockerande2epost through it; consumer jobs that cannot go through them (an inline npm publish) call it directly.release-pr-cancel.ymlandrelease-complete.ymlflip the head message to Cancelled / Completed and move the Linear release;release-startcreates the Linear release (steps/linear-release, optionalop-linear-pipeline-key-path).notify-failurejob.deploy-vercel: build-only secrets (op-build-secret-refs),gated, the output guard against mask scrubbing.deploy-docker:prepare-command, same ceremony.release-finalize: the two thread messages +after-release-note.steps/gh-ensure-pr-comment,lib/markers.js(one parser for the release markers).Examples cover the whole lifecycle per scenario (
release-changesets-monorepo.yml,deploy-production.yml,publish-npm.yml,release-semantic-release.yml).contracts/consumers.jsonregisters the call shapes of aragon/app, aragon/app-backend and aragon/aragon-indexer (their PRs follow and reference@main; the SHA pin is a follow-up once the modules settle).Design:
docs/release-design.md§9.🤖 Generated with Claude Code