Repository navigation
docs: release v1.3.0 — every task goes through /dispatch - #38
Merged
Merged
Conversation
A minor release for teams with the parallel-agents module (#37, decision 0020): the main checkout's session takes every task and hands it to a new session in a worktree of its own, by the route the project's worktree.conf gives, and the plugin carries /dispatch. Unreleased becomes v1.3.0, with the upgrade from v1.2.x. Decision 0017 gets a dated clarification: "has to act" means something stops working until the team acts. A migration /aplyca-adf:upgrade carries out, or a changed rule in an opt-in module, is minor — as v1.2.0 and v1.3.0 shipped. plugin.json 1.3.0; both READMEs name the release. 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
1 participant
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.
Release v1.3.0, a minor release for teams with the
parallel-agentsmodule (#37, decision 0020). The main checkout's session now takes every task and hands it to a new session in its own worktree, by the route the project'sworktree.confgives. The plugin also carries/dispatch. Nothing changes for a project without the module.Changes
CHANGELOG.md: Unreleased becomesv1.3.0 — 2026-10-06 — Every task goes through /dispatch, with the upgrade from v1.2.x.plugin.json:1.3.0. The root README's "latest" line and the plugin README's"ref"name the release./aplyca-adf:upgradecarries out, or a changed rule in an opt-in module, makes a minor release, as v1.2.0 and v1.3.0 shipped. This settles the version question I raised in feat: every task through /dispatch, and the plugin carries it #37.After merge
v1.3.0on the merge commit, then rungh release create --latest --verify-tag, with the CHANGELOG section as the notes. Both happen on your go-ahead./aplyca-adf:dispatchand check that the chip's worktree gets.env. That check was left open in feat: every task through /dispatch, and the plugin carries it #37.Verification
./evals/run-evals.sh: all static suites pass, including the check thatplugin.jsonmatches the newest CHANGELOG release.🤖 Generated with Claude Code