Repository navigation
ci: approve the release pull request's own CI run, found by its branch - #398
Merged
Merged
Conversation
…n main release.yml looked it up by its `autorelease: pending` label, which release-please had not yet added for 0.2.0-beta.2: the lookup came back empty and CI was dispatched on main, leaving the release pull request without `ci-ok`. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
futrime
changed the title
This was referenced Oct 13, 2026
futrime
added a commit
that referenced
this pull request
Oct 13, 2026
) Cherry-picks what landed on `main` since `release/0.2` was last brought up to date, for `0.2.0-beta.2`. #392 and #395 are skipped: #396 brought them already. fix: line up the sidebar's top row with the traffic lights, and every row on one column (#399) fix(desktop): keep a strip for the traffic lights over the sidebar's top row (#402) fix(desktop): keep the traffic lights' strip across the whole window (#403) ci: write a release's notes since the release before it, not its last pre-release (#387) ci: find the release pull request by its branch to run CI on, never on main (#398) ci: approve the release pull request's own CI run instead of dispatching one (#400) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
futrime
added a commit
that referenced
this pull request
Oct 14, 2026
…message (#447) Cherry-picks what landed on `main` since `release/0.2` was last brought up to date, for `0.2.0-beta.3`. #387, #392, #395, #398, #399, #400, #402 and #403 add nothing to the changelog, since #396 and #404 brought them already. Afterwards `release/0.2` holds the same code as `main`, and only the version files, `CHANGELOG.md` and `release-please-config.json` differ. feat: chat like Claude, no all-sessions log, Exomyth fixes, split profiling, TUI parity (#422) feat: many chats, each its own epic beside the workspace's flow, folding away when idle (#427) feat(runtime): let docker and swarm runtimes share a host: name prefix, exec user, running container (#426) fix(coganchor): let turns working in one mirror at once see each other's work (#423) fix(flows): keep and carry on supervised sessions, whose CLI runs here in a mirror (#424) fix(telemetry): scrub reports as bundles are, timings and profiles too, only where started (#439) fix(coganchor): keep the turns of the shared-mirror test in the mirror at once (#442) fix(agents): retry Codex's dropped streams and start every harness in a virtual config home (#425) feat: rewrite specs as api/ and features/, pick the btw agent per epic, refuse cross-machine workspace hooks (#444) fix(coganchor): build a harness's virtual home on its own machine under afar (#445) BEGIN_NESTED_COMMIT feat(runtime)!: say where a harness runs with one setting, not four placements (#446) BREAKING CHANGE: runtimes take `harness` instead of `affinity`, and work on another machine with no setting no longer drops to a harness here when the CLI is missing or a gating hook is hung: set the runtime's harness to `local`. A saved `affinity` is still read, as its first entry with `self` as `env`. END_NESTED_COMMIT
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cutting 0.2.0-beta.2 (#397) showed two problems in
release.yml's "Run CI on the release pull request" step:autorelease: pendinglabel, which release-please adds only after it opens the PR. The lookup came back empty, andgh workflow run ci.yml --ref ""ran CI onmain.ci-okdoesn't satisfy the branch rule anyway. I dispatchedci.ymlon chore(release/0.2): release 0.2.0-beta.2 #397's head by hand and it passed, but merging was still refused withRequired status check "ci-ok" is expected. The PR's ownpull_requestrun does count, but on a PR a workflow opened, that run waits for approval (action_required). Approving it is what unblocked chore(release/0.2): release 0.2.0-beta.2 #397. beta.1's PR chore(release/0.2): release 0.2.0-beta.1 #386 also merged on itspull_requestrun; both of its dispatched runs had failed.The step now:
release-please--head branch, and fails with::error::if none is open;action_requiredci.ymlrun, then approves it withactions: write;docs/contributing/releasing.mdis updated to match.Test plan
release/0.2, returnsrelease-please--branches--release/0.2--components--hmzPOST /actions/runs/{id}/approve) starts chore(release/0.2): release 0.2.0-beta.2 #397's held runrelease.ymlGITHUB_TOKENitself may approve. The nextrelease.ymlrun will show it; if it can't, the step fails loudly and a maintainer approves the run by hand.🤖 Generated with Claude Code