Skip to content

chore(release): prepare @aictrl/cli 0.4.6 #133

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
byapparov merged 1 commit into from
Oct 7, 2026
Merged

chore(release): prepare @aictrl/cli 0.4.6 #133

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 14 additions & 12 deletions RELEASING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,18 +36,20 @@
`sandbox` before `main`; verify a sandbox review persists MCP findings and
a stalled stream reports a timeout rather than waiting for the job limit.

## 0.4.5 candidate

- MCP tools are discovered once per connection and retained for both the
startup catalog and model turns (CLI #127). Tool-list change notifications
refresh that catalog; a failed refresh or closed connection stops the next
turn with an actionable error, instead of submitting a reduced toolset.
A successful later notification or reconnection restores discovery health.
Initially unavailable optional MCP servers keep their existing behavior.
- Release version checks and npm propagation handling address CLI #126.
- The executor enables the existing five-minute model stream idle guard in
application #5891. The CLI retains its generic opt-in default; local tools
retain the extended allowance and explicit operator overrides remain valid.
## 0.4.6 candidate

@aictrl-dev aictrl-dev Bot Oct 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 0.4.6 regressions missing from release test gate.

🤖 Fix with your agent 
Fix this code review finding (aictrl-dev/cli PR #133, RELEASING.md:39-52):

Problem: 0.4.6 regressions missing from release test gate
Detail: The candidate section is bumped to 0.4.6, whose headline feature is structured output (#129), but the release-regression `bun test` list in step 2 of this document still contains only the 0.4.5-era suite and was not extended in this PR. Dedicated regressions for the new feature exist (packages/cli/test/session/structured-output.test.ts, packages/cli/test/session/structured-output-integration.test.ts, packages/cli/test/cli/run-schema-v1.test.ts), so the documented pre-release gate no longer covers the current candidate's features, breaking the file's own convention that the regression list tracks the candidate.
Suggested fix: Extend the step 2 regression `bun test` list with the structured-output suites, e.g. add `packages/cli/test/cli/run-schema-v1.test.ts packages/cli/test/session/structured-output.test.ts packages/cli/test/session/structured-output-integration.test.ts` (plus any `run-output-schema` regression if present on the branch) to the documented pre-release command.

Implement the fix on the PR head branch and add a regression test that fails before the fix and passes after.
Why this matters

The candidate section is bumped to 0.4.6, whose headline feature is structured output (#129), but the release-regression bun test list in step 2 of this document still contains only the 0.4.5-era suite and was not extended in this PR. Dedicated regressions for the new feature exist (packages/cli/test/session/structured-output.test.ts, packages/cli/test/session/structured-output-integration.test.ts, packages/cli/test/cli/run-schema-v1.test.ts), so the documented pre-release gate no longer covers the current candidate's features, breaking the file's own convention that the regression list tracks the candidate.

## 0.4.6 candidate

- `aictrl run --output-schema <file>` enforces a JSON Schema on the final
  result with bounded corrective retries (`--output-schema-retries`, default 2)
  and writes only the validated value to `--output-result <file>` (#129).
  Exit 2 is a schema configuration error; exit 3 is a structured-output failure.
  New NDJSON events `structured_output_rejected` and a terminal
  `structured_output` are additive (schema "1"). Runs without a schema are
  unchanged.


- `aictrl run --output-schema <file>` enforces a JSON Schema on the final
result with bounded corrective retries (`--output-schema-retries`, default 2)
and writes only the validated value to `--output-result <file>` (#129).

@aictrl-dev aictrl-dev Bot Oct 7, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚪ Issue refs drop 'CLI' prefix used in prior section.

Suggested change
and writes only the validated value to `--output-result <file>` (#129).
Write "(CLI #129)" on the three new references to match the previous section's style, or normalize the whole file to one style.
🤖 Fix with your agent 
Fix this code review finding (aictrl-dev/cli PR #133, RELEASING.md:43):

Problem: Issue refs drop 'CLI' prefix used in prior section
Detail: The replaced section used "CLI #127" / "CLI #126" for issue references, while the new 0.4.6 section uses bare "(#129)" three times yet keeps the "application #5960" prefix style. The mixed reference style deviates from the file's own prior convention for first mentions.
Suggested fix: Write "(CLI #129)" on the three new references to match the previous section's style, or normalize the whole file to one style.

Implement the fix on the PR head branch and add a regression test that fails before the fix and passes after.
Why this matters

The replaced section used "CLI #127" / "CLI #126" for issue references, while the new 0.4.6 section uses bare "(#129)" three times yet keeps the "application #5960" prefix style. The mixed reference style deviates from the file's own prior convention for first mentions.

Exit 2 is a schema configuration error; exit 3 is a structured-output failure.
New NDJSON events `structured_output_rejected` and a terminal
`structured_output` are additive (schema "1"). Runs without a schema are
unchanged.
- `--attach` request shapes are fixed for the legacy SDK client (#129).
- A stalled models.dev catalog body no longer surfaces as an unhandled
`TimeoutError` (#129).
- Executor adoption (pin bump plus entrypoint flags) is tracked separately in
application #5960.

Publication and executor promotion are separate gates. Preparing this candidate
PR does not publish npm packages or deploy an executor image.
2 changes: 1 addition & 1 deletion bun.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion packages/cli/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"$schema": "https://json.schemastore.org/package.json",
"version": "0.4.5",
"version": "0.4.6",
"name": "@aictrl/cli",
"description": "Headless execution engine for AI agent skills",
"type": "module",
Expand Down
Loading