Processes/software — the spec, build, review, ship loopsoftware
Cut a release — software processCut a release
The release ritual: draft the changelog from merged PRs, tag the release behind an approval, publish notes, watch errors after rollout, and roll back if it goes sideways.
Changelogs, tags, and release notes are pure API work. Deciding to roll back is a human call.
Current agent ceiling
An agent can run 4 of 5 steps — 1 of them behind a human approval gate ⏸
No workaround yet (1): Roll back if needed (needs a human)
How it runs
Route-coded block flow: emerald = agent, amber = manual form/portal, red = needs a human. ⏸ approval gate · ⏳ async wait.
01Draft the changelog
agent1 API call
- GET /repos/{owner}/{repo}/compare/{base}...{head}
02Tag the release
agent1 API call
- POST /repos/{owner}/{repo}/releases
04Monitor errors post-release
agent
Sentry49⏳ async
05Roll back if needed
humanThe market options
Each role resolves against its arena’s live leaderboard — the default is the process’s canonical vendor, alternatives ranked by agent-readiness.
GitHubdefault71/100 agent-ready
GitLab54/100 agent-ready
Gitea34/100 agent-ready
Bitbucket19/100 agent-ready
Notiondefault59/100 agent-ready
Linear56/100 agent-ready
monday.com52/100 agent-ready
Asana45/100 agent-ready
ClickUp35/100 agent-ready
Jira24/100 agent-ready