From 7f5834cafedb9e919765f4e5d684113c0fe24ffb Mon Sep 17 00:00:00 2001 From: Bulat Yapparov Date: Thu, 21 May 2026 22:56:09 +0100 Subject: [PATCH] chore: bump @aictrl/cli to 0.3.5 and @aictrl/util to 1.2.17 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit v0.3.4 release (#71 + #72 fixes) couldn't actually publish @aictrl/cli because the publish workflow doesn't auto-stamp AICTRL_VERSION into the main package.json `version` fields — only platform binaries get the release version. On v0.3.4 the workflow tolerated "already-published" errors for cli 0.3.3 / util 1.2.16 / sdk 0.1.2 and the smoke test correctly caught it (ETARGET: No matching version found for @aictrl/cli@0.3.4). Bump cli and util so v0.3.5 actually publishes new versions carrying the resolver + exit-code fixes. Skip sdk: its catalog: deps are only in devDependencies, ignored by npm consumers, so 0.1.2 is functionally installable. Follow-up worth filing: publish.yml should stamp AICTRL_VERSION into all package manifests, not just platform binaries, so future releases don't need manual version bumps. Refs #71 #72 Co-Authored-By: Claude Opus 4.7 (1M context) --- packages/cli/package.json | 2 +- packages/util/package.json | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/cli/package.json b/packages/cli/package.json index d45953c..fe47b76 100644 --- a/packages/cli/package.json +++ b/packages/cli/package.json @@ -1,6 +1,6 @@ { "$schema": "https://json.schemastore.org/package.json", - "version": "0.3.3", + "version": "0.3.5", "name": "@aictrl/cli", "description": "Headless execution engine for AI agent skills", "type": "module", diff --git a/packages/util/package.json b/packages/util/package.json index 197ebd4..c97adcc 100644 --- a/packages/util/package.json +++ b/packages/util/package.json @@ -1,6 +1,6 @@ { "name": "@aictrl/util", - "version": "1.2.16", + "version": "1.2.17", "private": false, "type": "module", "license": "MIT",