Repository navigation
release: 4.0.0 version bumps, CHANGELOG cut, major-release landing flow [95c660e2] - #623
Merged
Merged
Conversation
…w [95c660e2] Version bumps (server 4.0.0, plugin 4.0.0, mod 0.2.0), CHANGELOG 4.0.0 cut with empty [Unreleased], prepare-release X1 flow, UPGRADE_BACKUP stamp and smoke wording fixes. Seat: implementer Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…lease cut [95c660e2] Four tests pinned item bullets under [Unreleased]; the cut moves them into ## [4.0.0] - 2026-10-17, so each test now anchors on that heading. Oracles unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…branch that absorbs main [95c660e2] A simulated release/4.0 -> main merge conflicts in 60+ files, so the landing branch records main as a parent with -s ours after a twin audit (21/22 covered; #574 needs a 4.0 twin, item a3d6a64a). main's [Unreleased] 3.x bullets ship from release/3.x, not folded into 4.0.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…660e2] N1 resolve-changelog path; N2 conflict count; N3 fold release/4.0 [Unreleased] into [4.0.0] before the landing leaves draft; N4 drop the never-released dogfood freeze guard from 4.0.0; N5 release/3.x pin recipe caveats. The #621 phase-guard bullet moves beside the other Fixed bullets in ### Plugin. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
P26 (X1), the 4.0.0 release PR into
release/4.0. This PR does not land onmain, does not tag, and does not publish; those steps are the user's gate.version.properties4.0.0;server.jsonversion4.0.0, OCIghcr.io/jpicklyk/task-orchestrator:4.0.0, a description naming profiles and runs, and theUPGRADE_BACKUPstamp spelled<yyyyMMddTHHmmssZ>; plugintask-orchestrator4.0.0 inplugin.jsonand.claude-plugin/marketplace.json;task-orchestrator-mod0.2.0.CHANGELOG.md:[Unreleased]cut into## [4.0.0] - 2026-10-17with "Upgrading from 3.x" on top and the Plugin 4.0 entry, with an empty## [Unreleased]left above it. The lock wait (300 s, no env key) is release-noted, and the.bakstamp has one spelling everywhere.claude-plugins/CLAUDE.md: the version and compatibility tables, with the 3.x pin written as therelease/3.xref (P25 D2)..claude/skills/prepare-release/SKILL.md: the point-release path (both plugins, categories Added/Changed/Removed/Fixed/Security/Plugin, the empty-[Unreleased]rule, the data-step andUPGRADE_BACKUPlines kept in a major release body) and a "Major release landing" flow. That flow covers:release/3.xfirstland/4.0.0branch that retires theguardjob and recordsmainwithmerge -s oursguardcheckmainfleet-deployment.mdand the smoke scripts: the two-boot wording and the 4.0.0 tag.Test Results
:current:test+ktlintCheck,--rerun-tasks): BUILD SUCCESSFUL in 6m 18s. The version-embedding goldens normalizemetadata.version.node --testoverscripts/tests/*.test.mjsandhooks/tests/*.test.mjs: 2444 pass, 0 fail. Four tests that pinned item bullets under[Unreleased]now read## [4.0.0](oracles unchanged,97416043).gen-call-shapes.mjs --check: fresh.Review
Independent docs-accuracy review (Fable,
task-orchestrator:reviewer): Pass, 0 blocking. Every operator-facing claim was opened at its source line (backup stamp, 300 s lock, failure names, env parity across 46 names, docker-publish/sync-wiki/test/guard workflows, both rulesets, themerge -s oursrecipe and the 270 conflicting paths). N1-N5 were fixed ine858530d: the resolve-changelog path, the conflict count, folding post-cut[Unreleased]before the landing leaves draft, dropping the never-released freeze-guard bullet, and therelease/3.xpin caveats. N6 and N7 were accepted (details inorchestrator-confirmation).origin/release/4.0(#620-#622) was merged in at3d6f94ac; its two Plugin bullets sit inside## [4.0.0].Docs
CHANGELOG.mdclaude-plugins/CLAUDE.md.claude/skills/prepare-release/SKILL.mdcurrent/docs/fleet-deployment.mdMCP
95c660e2-617b-49ef-8eb3-4f1820f9fb8b(P26, W7; runr-202610171521-95c660e2). The landing twin audit found main's #574 without a 4.0 twin; twin itema3d6a64a. Bullets merged intorelease/4.0after this branch's base are folded into## [4.0.0]before merge.🤖 Generated with Claude Code