Skip to content

AGENTS.md opens the release approval in the user's browser #55

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
czj merged 1 commit into from
Nov 7, 2026
Merged

AGENTS.md opens the release approval in the user's browser #55

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,8 +70,10 @@ environment on GitHub.
`bin/release minor --dry-run`, then `bin/release minor --yes` (or `patch`, `major`). It opens `release/vX.Y.Z`,
waits for it to merge itself, pushes the signed tag. Signing fails: the user fixes it, never an unsigned tag.
Interrupted after the merge: `bin/release --tag X.Y.Z`.
4. The tag runs `release.yml`, which waits for the user to approve the `release` environment (the run's Review
deployments), then publishes to RubyGems and GitHub. Tell the user, then check RubyGems.
4. The tag runs `release.yml`, which waits for the user to approve the `release` environment, then publishes to
RubyGems and GitHub. Open that run in their browser, where they click Review deployments, `release`, Approve:
`gh run view --web $(gh run list --workflow release.yml --limit 1 --json databaseId -q '.[0].databaseId')`.
Then check RubyGems.

RubyGems trusts only that workflow: never `gem push`, except a new gem name's first version. `bin/release` and
`release.yml` are identical in all four gems.
Loading