From 7cc407aceba63e2c26f5ee38f4d8e7b4687c1f4d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Joubert?= Date: Sat, 7 Nov 2026 23:54:16 +0100 Subject: [PATCH] AGENTS.md opens the release run of the new tag --- AGENTS.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/AGENTS.md b/AGENTS.md index 9350b32..9d98427 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -90,7 +90,9 @@ environment on GitHub. 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, 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')`. + `gh run view --web $(gh run list --workflow release.yml --branch vX.Y.Z --json databaseId -q '.[0].databaseId')`, + once the run exists: it starts a few seconds after the tag, and without `--branch` the previous release's run + opens. Then check RubyGems. RubyGems trusts only that workflow: never `gem push`, except a new gem name's first version. `bin/release` and