Skip to content

chore(release): promote v0.6.24 to main - #66

Merged
bacsystem merged 4 commits into
mainfrom
develop
Jul 24, 2026
Merged

chore(release): promote v0.6.24 to main#66
bacsystem merged 4 commits into
mainfrom
develop

Conversation

@bacsystem

Copy link
Copy Markdown
Owner

Summary

Promotes develop to main: v0.6.24.

  • bin/parse-plan.js / bin/plan-remainder.js: now report parallelWidth in their JSON output.
  • /cys:run-plan and /cys:flow: offer to set maxConcurrency automatically when the plan's parallelWidth exceeds 6, and pass the chosen value through to the Workflow launch args. runDag's maxConcurrency cap has existed since v0.6.15, but neither command surfaced it until now.
  • Both READMEs updated.

Full details in CHANGELOG.md.

Merge

Use "Create a merge commit" (squash is disabled repo-wide) to keep shared ancestry with develop intact.

…s output

maxConcurrency (runDag's optional concurrency cap, since 0.6.15) had no way
to reach the interactive commands: /cys:run-plan and /cys:flow never saw the
plan's inferred parallelism before launching, so they couldn't decide whether
capping was worth offering. computeParallelWidth(graph) already existed
(0.6.18, used only in the workflow's own final summary) — both CLIs now
report it in their JSON so the commands can read it before the run starts.
runDag has supported an optional maxConcurrency cap since 0.6.15, but
neither /cys:run-plan nor /cys:flow ever asked about it or passed it
through — a user had to bypass the command and invoke the Workflow tool
by hand to use it at all.

Both commands now read parallelWidth from the parsed plan's JSON
(previous commit) and, only when it exceeds 6, mention that the plan can
run that many tasks at once and ask whether to cap it with
maxConcurrency. Narrower plans are never asked — a low parallelWidth
never benefits from capping. The chosen value (or its absence) now flows
through to the Workflow launch args in both commands. Documented in both
READMEs.
…commands

feat(commands): offer maxConcurrency automatically for wide plans
@bacsystem bacsystem self-assigned this Jul 24, 2026
@bacsystem
bacsystem merged commit 5a7e3d6 into main Jul 24, 2026
0 of 2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant