chore(main): release 1.266.0 - #2417
Conversation
What merging this release deploysDeploy targets for 0f14965: 2 of 4 Workers — bot, resident
Unclassified paths: none. Judged per Worker against the commit it is serving right now. Re-rendered by the |
There was a problem hiding this comment.
LGTM: Release 1.266.0 is consistent with merged #2413, the bot-only production deploy target, and green head checks; Depot tokens remain optional and separately provisioned.
Note
Approved · head 7f52ec6 · no findings
Full review
Approved at exact head 7f52ec6879bc88537db1d441a4b916c861d203f8; no concrete release issues found. The head contains merged #2413 (a941941), all 29 reported head checks completed successfully or were skipped, and the release deploy-targets comment identifies bot only. Deployment does not provision DEPOT_API_TOKEN or DEPOT_CI_BRIDGE_TOKEN; both remain optional, separate secrets. This sandbox does not expose the review run ID or its permalink, so I cannot report those without guessing.
7f52ec6 to
d40807c
Compare
There was a problem hiding this comment.
LGTM: Release 1.266.0 contents, bot-only deploy target, and current-head CI check out; Depot credentials and live-child proof remain post-deploy gates.
Note
Approved · head d40807c · no findings
Full review
No findings at d40807c; verdict: approve. Release 1.266.0 includes the merged #2418 fix, the derived plan deploys only the bot Worker, and all current-head CI checks completed successfully or were skipped as expected. Depot secret provisioning and proof from a real coding child remain separate post-deploy gates, not evidence supplied by this release review.
Review run ID and run permalink were not exposed to me; I can’t report them reliably. PR #2417.
39239b4 to
3f3aa96
Compare
3f3aa96 to
0f14965
Compare
There was a problem hiding this comment.
LGTM: Release metadata is internally consistent at the assigned PR head; requested SHA and deploy-target count do not match the live PR.
Note
Approved · head 0f14965 · no findings
Full review
I approved the release metadata at 0f14965, not at the requested 3f3aa96. The checkout and PR #2417 both identify 0f14965 as the head, so this verdict does not approve 3f3aa96.
The reviewed head contains #2413, #2418, #2419 and #2407. Its CI and CodeQL checks are green, but the deploy-target comment says bot and resident (2 of 4 Workers), not bot only. #2407 remains disabled local account-link consent, not a live cutover. Depot credential provisioning and real-child proof remain post-deploy gates.
Run ID and run permalink were not available to me; I cannot report them reliably.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
1.266.0 (2026-09-26)
Features
Bug fixes
This PR was generated with Release Please. See documentation.