Skip to content

chore(release): plan v2026.10.4 - #1813

Merged
kryptobaseddev merged 8 commits into
mainfrom
chore/release-plan-v2026.10.4
Oct 4, 2026
Merged

kryptobaseddev merged 8 commits into
mainfrom
chore/release-plan-v2026.10.4

Conversation

@kryptobaseddev

@kryptobaseddev kryptobaseddev commented Oct 3, 2026 •

Copy link
Copy Markdown
Owner

Release plan for v2026.10.4 (hotfix), generated from main da4eac935.

Plan sha256: 442383652c78a85e6c14c4337157f8526369a6409506016d5f1cb9a31bd53bdf

release-prepare is not dispatched from here; main dispatches it after this merges.

🤖 Generated with Claude Code

kryptobaseddev and others added 5 commits October 3, 2026 09:00
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… T13106, T13104)

Provisional hotfix plan. It is regenerated when #1797 (T13102) and the
P0 PRs (T13122, T13123, T13124) merge. The CHANGELOG body equals
meta.releaseNotes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…d hook, no implicit whole-suite evidence, CLI startup memory, heap/worker/typecheck caps

Regenerated from main da4eac9 with `cleo release plan v2026.10.4 --tasks
T13103,T12472,T13100,T13104,T13106,T13122,T13136,T13119,T13150`: the tasks
that are closed (owner decision: option C, no override). Every other merged
PR since v2026.10.3 still ships as commits. The notes lead with the update
line and highlights in the owner's order (#1826, #1811, #1818, #1812/#1820,
#1808/#1810/#1824), then "Also in this release" (#1797, #1816, #1817, #1807),
then the generated sections. The CHANGELOG body equals meta.releaseNotes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kryptobaseddev
kryptobaseddev marked this pull request as ready for review October 4, 2026 02:43
kryptobaseddev and others added 3 commits October 3, 2026 19:57
…1811 and #1818 highlights (review)

The #1826 highlight names the recovery (superseded-store --reconcile --dry-run, then --reconcile; additive, verified, legacy files untouched). The #1811 highlight no longer claims every allow-rule command is governed: plain pre-approved forms are queued, anything else is warned; it names the files written (kept out of git), the opt-out and doctor heavy-command-hook --fix. The #1818 heading no longer claims whole suites never run. CHANGELOG body still equals meta.releaseNotes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…172 known limit

team-p0-startup verified --reconcile recovers stranded tasks and memory on 2026.10.3, with one silent-loss case (T13172): a task created after upgrading can take an old task's id, and that old task is not copied. The line now says so, tells users who created tasks after upgrading to wait for the fix, and to keep .cleo/tasks.db. CHANGELOG body still equals meta.releaseNotes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ading to 2026.10.2 or 2026.10.3 (review)

The macOS pressure backend behind the deferral (#1777, T12981) first shipped in v2026.10.2 (its merge eb3f774 is in v2026.10.2, not v2026.10.1), so 10.2 users are exposed too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@kryptobaseddev

Copy link
Copy Markdown
Owner Author

Independent review: review-p0 APPROVED at 4c03e2d. Plan sha256 442383652c78a85e6c14c4337157f8526369a6409506016d5f1cb9a31bd53bdf (verified against the file at that head). Diff is release metadata only (changeset archive moves, .cleo/release plan files, CHANGELOG); CHANGELOG body equals meta.releaseNotes. Recovery wording verified in a sandbox against released 2026.10.3 (team-p0-startup); the id-collision limit is tracked in T13172. Main push CI on parent da4eac9 (run 37171533531) green on all 4 ubuntu shards. PR CI green (77 pass, 0 fail).

@kryptobaseddev
kryptobaseddev merged commit 14f8330 into main Oct 4, 2026
89 checks passed
@kryptobaseddev
kryptobaseddev deleted the chore/release-plan-v2026.10.4 branch October 4, 2026 03:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant