From 3b45846650336118c1c22f885c5542b3c48df3a8 Mon Sep 17 00:00:00 2001 From: Hebilicious Date: Wed, 30 Sep 2026 21:54:13 +0700 Subject: [PATCH 1/2] docs(agents): pre-authorize changesets release pull requests Merging a release pull request needed an explicit instruction for that PR, so an agent that merged a feature had to stop and ask before merging the release the workflow opened for it. That branch never goes green: its CI run sits at `action_required` and the runs that do execute fail, which is why the previous release PR was merged with a red board. The rule now names the exception, so the release is not gated on an answer that only exists in one session. --- AGENTS.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index edf34ad..bb01c98 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -20,9 +20,14 @@ standard library or writing code from first principles. - Run `git status` before editing and review the complete diff afterward. Preserve unrelated changes and commit only when explicitly requested. - Open a pull request and stop there. Never merge a pull request that a human has not reviewed, - including release pull requests, and never merge one because the work looks finished or the - checks are green. Merging needs an explicit instruction from the user for that specific pull - request, and opening a pull request is not that instruction. Report the pull request URL and wait. + and never merge one because the work looks finished or the checks are green. Merging needs an + explicit instruction from the user for that specific pull request, and opening a pull request + is not that instruction. Report the pull request URL and wait. +- A changesets release pull request is the exception, and it is pre-authorized: when the release + workflow opens one for work that was just merged, merge it as soon as GitHub reports it + mergeable. That branch never gets a green CI gate, its workflow run sits at `action_required`, + and the runs that do execute on it fail, so waiting for a green board deadlocks the release. + Merging it publishes the packages to npm and JSR, which is the intended effect. - Define repository operations in `moon.yml` or `.moon/tasks/**/*.yml`, not `package.json` scripts. Run existing operations through their Moon targets; use pnpm directly only for dependency management. From cf98a81975be81bbae0edc9b8e87defb4fa93d7e Mon Sep 17 00:00:00 2001 From: Hebilicious Date: Wed, 30 Sep 2026 23:02:37 +0700 Subject: [PATCH 2/2] docs(agents): say the release rule in one line --- AGENTS.md | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index bb01c98..092e664 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -23,11 +23,9 @@ standard library or writing code from first principles. and never merge one because the work looks finished or the checks are green. Merging needs an explicit instruction from the user for that specific pull request, and opening a pull request is not that instruction. Report the pull request URL and wait. -- A changesets release pull request is the exception, and it is pre-authorized: when the release - workflow opens one for work that was just merged, merge it as soon as GitHub reports it - mergeable. That branch never gets a green CI gate, its workflow run sits at `action_required`, - and the runs that do execute on it fail, so waiting for a green board deadlocks the release. - Merging it publishes the packages to npm and JSR, which is the intended effect. +- An authorized pull request authorizes its release: merge the changesets release pull request + the workflow opens for it once it is mergeable. That branch never gets a green CI gate, so + waiting for one deadlocks the release. - Define repository operations in `moon.yml` or `.moon/tasks/**/*.yml`, not `package.json` scripts. Run existing operations through their Moon targets; use pnpm directly only for dependency management.