Skip to content

chore(main): release 1.213.0 - #1032

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

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

Conversation

@coreplane-infra

@coreplane-infra coreplane-infra Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.213.0 (2026-09-14)

Features

  • agents: pi 0.85.1 in both execution images, a preset's harness field with its config knob, and an exec's caller environment — the ground the pi harness lands on (#1042) (8179e7a)
  • dispatcher: the router is on by default — a fresh installation routes a plain message from its first day, help says "describe what you want", and the card says how to override a route (#1038) (41a734a)
  • harness: the coding preset can run on pi — pi in the container with the run's bearer as its only key, every RPC event bridged into the run's own events and spans, our tools and tool rules as its extension, dark behind harness: pi (#1043) (8c95dd5)
  • runs: a run's files move by reference — the artifact event names the store key, the run page serves each file through its own authorized route, and the Files block lists them with images inline (#1045) (0146e37)
  • tools: the artifact store seam — a run's files can move by reference through one private R2 bucket the bot signs URLs for, with the config section, three bot secrets and the /healthz fact; absent the section, nothing changes (#1040) (d35050e)

Bug fixes

  • dispatcher: the router reads a terse "fix it" as a coding ask — imperative fixtures join the replay, and the compound rule meets its bar at the live model (#1051) (f99535d)
  • harness: a fresh pi run is prompted with the request, not the thread's oldest turn — the earlier turns become the session pi starts from, and a single-turn thread is unchanged (#1048) (ea57f04)
  • keep error-code diagnoses out of the secret redactor and make the onboard not-in-installation refusal actionable (#1041) (33d4e2b)
  • resident: a container whose runtime never answers heals itself — the unreachable probe is named, counted and escalated (short re-arm, stop, destroy and restore from snapshot, then down), with an admin recreate-container op (#1046) (78f5409)

Documentation

  • docs: record 0033 proposes the artifact store — run files move by reference through one private R2 bucket in both directions, and the run record keeps the key (#1033) (80e3664)
  • docs: the execution ledger for record 0033 — eight units that move run artifacts through R2 in both directions, outbound first, each inert until the store is configured (#1036) (3192767)
  • the front door is the first thing a newcomer meets — every intro says describe what you want, commands wait for whoever digs, and the pictures show a routed run (#1037) (0318334)
  • the front door, the runner and the budgets read as built — every page says a plain message routes itself, no pause exists, turns are a guard, and the plan's graph matches its text (#1031) (bdf2504)

This PR was generated with Release Please. See documentation.

@github-actions

github-actions Bot commented Sep 14, 2026

Copy link
Copy Markdown

What merging this release deploys

Deploy targets for 929b46b: 4 of 4 Workers — memory, bot, resident, sandbox

Worker Decision Judged against Why
memory deploy live c3e94f9 src/agents/registry.ts (imported by deploy/cloudflare-memory/worker.ts)
src/core/redact.ts (imported by deploy/cloudflare-memory/worker.ts)
src/core/runEvents.ts (imported by deploy/cloudflare-memory/worker.ts)
src/core/runFriction.ts (imported by deploy/cloudflare-memory/worker.ts)
src/core/trace/workerTrace.ts (imported by deploy/cloudflare-memory/worker.ts)
bot deploy live c3e94f9 deploy/cloudflare/worker.ts
package-lock.json: dependencies of the root package changed — + aws4fetch 1.0.20
package.json
src/agents/registry.ts
src/artifacts/buildStore.ts
src/artifacts/config.ts
src/artifacts/contentType.ts
src/artifacts/keys.ts
… +52 more
resident deploy live c3e94f9 deploy/cloudflare-resident/Dockerfile
deploy/cloudflare-resident/worker.ts
deploy/cloudflare-resident/wrangler.template.jsonc
src/core/redact.ts (imported by deploy/cloudflare-resident/worker.ts)
src/core/trace/workerTrace.ts (imported by deploy/cloudflare-resident/worker.ts)
src/execution/residentRefresh.ts (imported by deploy/cloudflare-resident/worker.ts)
sandbox deploy live c3e94f9 deploy/cloudflare-sandbox/Dockerfile
src/core/redact.ts (imported by deploy/cloudflare-sandbox/worker.ts)
src/core/trace/workerTrace.ts (imported by deploy/cloudflare-sandbox/worker.ts)

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 9c8584c to 78b87ce Compare September 14, 2026 14:15
@coreplane-infra coreplane-infra Bot changed the title chore(main): release 1.212.1 chore(main): release 1.213.0 Sep 14, 2026
@coreplane-infra
coreplane-infra Bot force-pushed the release-please--branches--main--components--switchboard branch 9 times, most recently from 8667b17 to d90c391 Compare September 14, 2026 17:11
@justinhelmer

Copy link
Copy Markdown
Contributor

CI red on ci / bot / test 3 of 4 at d90c391 is the McpService OAuth concurrent-refresh race, filed as #1050: untouched by this release, passes 5/5 locally. Re-ran the failed Depot jobs.

@coreplane-infra
coreplane-infra Bot force-pushed the release-please--branches--main--components--switchboard branch from d90c391 to 929b46b Compare September 14, 2026 17:28
@justinhelmer
justinhelmer merged commit e6d1e5e into main Sep 14, 2026
30 checks passed
@justinhelmer
justinhelmer deleted the release-please--branches--main--components--switchboard branch September 14, 2026 17:30
@coreplane-infra

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

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