Repository navigation
v3.12.2
What's new
Bug Fixes
The ce:plan reference documentation still instructed orchestrators to dispatch research agents with a model argument on the Agent tool — an argument that doesn't exist in the tool's schema. When present, the dispatch silently degraded to a generic sub-agent with no configured model, which then inherited the session model and discarded the user's per-agent and per-category model assignments (#813).
This is the same defect previously reported in #784 and fixed across two skills in v3.10.2. That earlier pass missed this occurrence because it lives in a reference file rather than a skill body, and it was only caught this time by inspecting the published package rather than the source tree — the same line had already been corrected on the v2 maintenance branch by a wider sweep. A full sweep of bundled skills and agents confirms no remaining instance. The content-integrity gate checks that bundled agents omit a model field in frontmatter and validates literal subagent_type values, but nothing yet inspects prose for instructions to pass an unsupported argument — worth closing in a future pass.
Continuous Integration
The release job's dry-run flag ignored the value passed to it, in both directions: a dispatch from the default branch always published regardless of what the caller asked for, and a dispatch from any other branch never did (#810).
Two causes masked each other. The workflow expression relied on operator precedence that doesn't hold — && binds tighter than ||, and a workflow_dispatch input arrives as a string, so inputs.dry-run && 'true' evaluated truthy even when the caller passed false. The flag was therefore always true; the expression now compares against the string explicitly and parenthesizes the intent. A later step then forced the flag back to false whenever the run was on the default branch, which is what made real releases work at all and is why the first bug stayed invisible — but it also meant an explicitly requested dry run on the default branch performed a real release. With the expression corrected, that override step is redundant for every event the workflow handles, so it was removed rather than left to contradict the input. Pushes to the default branch are unaffected: they carry no inputs and evaluated false both before and after.
Also in this release
- deps: Update
bfra-me/.githubto v4.18.0 (#811).