bkinnightskytw
/
agent-orchestrator
mirror of https://github.com/ComposioHQ/agent-orchestrator.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs(release): clarify that the approval gate, not the tag push, controls who can cut a release 

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
Harshit Singh Bhandari 2026-07-04 04:15:23 +05:30
parent f19b577c87
commit 3118323300
No known key found for this signature in database
1 changed files with 6 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
frontend/docs/desktop-release.md
View File

@ -135,8 +135,12 @@ Approval is governed by required reviewers on the `release` environment
- @Vaibhaav-Tiwari
- @Priyanchew
Self-review is allowed (the tag pusher may approve their own run) and repo
admins can bypass. The current list is readable by anyone with repo access:
Anyone with write access can push the `desktop-v*` tag, but the build jobs
stay in `waiting` until one of the approvers above approves the run, so only
they can actually cut a release through the workflow. Self-review is allowed,
meaning a tag pusher who is also an approver may approve their own run; a
pusher who is not an approver still needs one of the five. Repo admins can
bypass the gate. The current list is readable by anyone with repo access:
```bash
gh api repos/AgentWrapper/agent-orchestrator/environments/release \