Skip to content

chore(main): release 1.261.4 - #2344

Merged
justinhelmer merged 1 commit into
mainfrom
release-please--branches--main--components--switchboard
Sep 24, 2026
Merged

justinhelmer merged 1 commit into
mainfrom
release-please--branches--main--components--switchboard

Conversation

@coreplane-infra

@coreplane-infra coreplane-infra Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.261.4 (2026-09-24)

Bug fixes

  • dispatcher: recover durable pushed heads (#2342) (afbad97)
  • ship: bind recovered pull requests before review (#2346) (b097224)

This PR was generated with Release Please. See documentation.

@github-actions

github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown

What merging this release deploys

Deploy targets for 21c1282: 2 of 4 Workers — memory, bot

Worker Decision Judged against Why
memory deploy live b727e58 deploy/cloudflare-memory/worker.ts
bot deploy live b727e58 src/channels/adminCoordinator.ts
src/core/coordinator/instanceStore.ts
src/core/dispatcher.ts
resident skip live 652eb70 no input changed
sandbox skip live 903ae28 no input changed

Unclassified paths: none.

Judged per Worker against the commit it is serving right now. Re-rendered by the release-please workflow on every merge to main; merging this PR runs deploy all --affected and deploys exactly the Workers marked deploy.

@coreplane-infra
coreplane-infra Bot force-pushed the release-please--branches--main--components--switchboard branch from ae6ada6 to 21c1282 Compare September 24, 2026 16:21
@justinhelmer
justinhelmer merged commit 9f4d0f4 into main Sep 24, 2026
30 checks passed
@justinhelmer
justinhelmer deleted the release-please--branches--main--components--switchboard branch September 24, 2026 16:27

@coreplane-switchboard coreplane-switchboard Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM: Standard release-please bump to 1.261.4; versions consistent and changelog matches the two commits since v1.261.3.

Note

Approved · head 21c1282 · no findings

Full review

I found no problems in this release PR. It moves the version from 1.261.3 to 1.261.4 in the same way in the manifest, both package.json files and the lockfile. The changelog lists #2342 and #2346, which are the only two commits on main since v1.261.3.

@coreplane-infra

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approved: coreplane-switchboard[bot] reviewed this PR and posted an LGTM verdict (see its review). This repository opted in through its REVIEW_BOT_LOGIN and REVIEW_BOT_ID variables.

@justinhelmer

Copy link
Copy Markdown
Contributor

Production receipt — v1.261.4

  • Justin human-merged unchanged release head 21c128271361059d3b7033d2f4b0325ed2ba5412 at 9:27:39 AM PDT; merge commit 9f4d0f4c9645ea67ecab3ede2455e658f38a7d4c.
  • The automatic release workflow completed successfully at 9:44:24 AM PDT; npm publish and every image publication passed.
  • Its generated affected plan selected memory + bot only: memory for deploy/cloudflare-memory/worker.ts; bot for src/channels/adminCoordinator.ts, src/core/coordinator/instanceStore.ts, and src/core/dispatcher.ts. Resident and sandbox skipped because no inputs changed; unclassified paths: none.
  • Bot is live and healthy on 1.261.4 / exact commit 9f4d0f4c9645ea67ecab3ede2455e658f38a7d4c (started 9:43:39 AM PDT, not draining).
  • Memory is healthy on exact commit 9f4d0f4c9645ea67ecab3ede2455e658f38a7d4c, build stamp 9:40:01 AM PDT.
  • The requested Switchboard review completed with zero findings on exact head 21c12827; its approval posted at 9:27:50 AM PDT, 11 seconds after the human merge. This preserves the actual sequence rather than implying the agent approval preceded merge.

This release prevents newly recovered/followed/branch-discovered pull requests from advancing without publication authority. It does not claim to heal retained units or enable same-unit recovery for existing #2338/#3589/CLI113/#2345 state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant