skaile-cli 6.0.0 → 6.2.0

package/CHANGELOG.md

@@ -1,5 +1,99 @@
 # Changelog
 
+## 6.2.0
+
+### Minor Changes
+
+- [#1106](https://github.com/skaile-ai/workspaces/pull/1106) [`7af33f2`](https://github.com/skaile-ai/workspaces/commit/7af33f2cf748dab42e4a5114e872ff97f55036ca) Thanks [@mortegro](https://github.com/mortegro)! - model-endpoint: `POST /v1/chat/completions` forwards `response_format`, `usage` and `provider` to OpenAI-compatible upstreams and reports upstream `usage.cost`
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Agents: `run`, `repl` and `rebuild` refuse an `agents:` block that `validate`, `install` and `check` reject, with the same line and exit 1 before the session starts (p1512). The `Connected Resources` block in rendered agent files names `skaile connector ops <id>` and `skaile connector run <id> <operation>` instead of the removed `skaile res` (p1710). Unknown keys in `agent:` and `agents:` (`agents.<id>.colour`, `agent.modle`, `model.preffered`) warn in `check`, `doctor`, `install`, `run` and `repl`, not only in `validate` (p1712).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Authoring: one verdict in every command. `library init --path <clone> --reader` and `--contributor` write nothing into the clone, so `library pull` and `sync` keep working; an owner is told that `skaile.manifest.yaml` changed and needs a commit (p1600). A scaffold placeholder body is a hard error in `asset import` and `add` too, with the `validate` line (p223). A `files:` entry that names a missing file fails the publish plan also when the entry has a `root:` (p1404). `library index` leaves a manifest entry alone when the asset's name is invalid and prints only the invalid-name line (p1601). A requires/dependencies error prints one line without `ManifestRequiresError:` (p1602). Path-less `validate versions` and `validate changelog` check the cwd like plain `validate`, and exit 1 outside a library instead of falling back to the factory assets (p1194). An unquoted `@publisher/name` in `agent.yaml`, `skaile.yaml` or any YAML manifest gets the double-quote hint (p1750). `library create flow` writes a strict v2 flow (`schemaVersion: 2`, one example `agent` node, no `globals:`), and a flow with `run:` nodes but no `schemaVersion: 2` is refused instead of read as an inert legacy flow (p489).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Consume fixes from the 6.1.0 critique:
+
+  - `check`, `doctor`, `validate` and every command that reads `skaile.yaml` refuse a `dependencies:` that is no list, a `dependencies:` item that is no string and a `sources:` that is no list with one `skaile.yaml — parse error: …` line and exit 1. `add` and `source add` write nothing (p1620).
+  - `diff`, `update`, `info`, `remove` and `why` give the `Did you mean agent:@pub/name` hint that `add` gives for a kindless ref (p1425).
+  - `source list|add|remove|show|sync` on a `skaile.yaml` whose root is not a map print the one parse-error line, no stack, and `validate` flags the file (p1421).
+  - `add --dry-run` prints the version once, and for an agent the files each harness writes (`.claude/agents/<name>.md`, ...), not a folder it never writes (p1621).
+  - A symlink cycle inside a library prints one `! <library>: asset scan truncated (cycle) - the symlink … points back into the tree …` line on stderr, not a raw timestamped `[runner:asset-scan]` record (p1622). New core export: `setWalkTruncationSink`.
+  - `add` of a manifest entry whose asset file now names another asset prints the `validate` line (`… now names "<name>" … run skaile library index <library>`) (p1603).
+  - `outdated` names `skaile install`, as `check` does, for a library asset that changed since the lock; a newer version still says `skaile update` (p1604).
+  - `run <flow> --dry-run` names every node skill that is not deployed, and the `skaile add` that fixes it (p1757). New `AssetManager.undeployedSkills()`.
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Harness: a `skaile.yaml` without `agent-config` uses one default, claude-sdk, which deploys to `.claude/`: `config show`, `run`, `repl` and `serve` now agree with `add` and `install` (p1670). After `harness set`, `install`, `list` and `add` name the copies of every other harness folder (`.claude/`, `.omp/`, `.codex/`) as stale, one line per folder (p1671). The repl banner names the agent the session runs; deployed agents are listed apart as not selected (p1672). The codex delegate warning is printed when an agent file was written, not when only a skill was added or restored (p1673). `config set model` prints `passed on as the model id <id> (no provider selected)` when no registry entry names or lists the model, and `config show` prints `passed on as:` (p1674). One message names the harness names of every command (`config set harness`, `harness set`, `init --harness`, `add --harness`, `integration --harness`, `run`, `repl`) (p1753). `install`, `list` and `config show` refuse an unknown `harness:` in `skaile.yaml` as `validate` does (p1754). A failed plugin install names its own reason for each plugin (p1272). `plugin install ./dir` and `file:../dir` exit 1 with one line that names the `name@file:/path/to/dir` form (p1737).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Protocol: the omp harness forwards `GIT_CONFIG_GLOBAL` to the agent's shell like every other harness (p1738). `serve` prints one `x` line for an unknown harness (p1731), a `--project-dir` that is no directory (p1732) and an `agent.definition` that does not resolve, which `validate` now refuses too (p1733). A `serve` option that takes a value and is followed by a flag names the missing value (p1730). The provisioned-mode error names `session_init` and its `secrets` map (p1734). `capability_result` failures always have the shape `{ok:false, code, message}` (p1736). A connector with `adapter:` gets the `validate` text, not a warning about the driver "undefined" (p1739). `serve --harness omp --model <x>` asks omp for its models and refuses a model it does not list before the ready line (p1334).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Restore fixes from the 6.1.0 critique:
+
+  - `install --locked` on a machine where the lock's library is not registered restores the files from the lock `url:` when every file has the locked hash, prints one notice line per library, exits 0, and `check` and `doctor` stay green (p1655). It never takes other bytes from a `sources:` repository instead (p128).
+  - Script files keep their exec bit in a store `add`, in `install --locked` from the lock url, in a store cache an older CLI filled, and in `../` compose folders copied next to an agent (p1657). New library exports: `isScriptBytes`, `restoreScriptModes`.
+  - `No skaile.yaml found` shows `--project-dir` after the command name, where it works (p1656).
+  - A factory asset is locked as `source: {url: factory, commit: <@skaile/workspaces version>}` instead of the ai-assets GitHub url at the all-zero commit (p1755). An older lock is still read and is rewritten by the next `add`, `install` or `update`. New core exports: `FACTORY_SOURCE_URL`, `LOCK_FACTORY_URL`.
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Store fixes from the 6.1.0 critique:
+
+  - `check`, `doctor`, `outdated` and `diff` no longer call the source of a freshly added store asset missing: the lock lookup uses the locked version, so assets of any store repo (not only ai-assets) pass (p380).
+  - A failed `skaile update` keeps the warm catalog cache on a REST-framed catalog too (p960).
+  - `source add` after `source remove` of the last source writes a block `sources:` list (p1690).
+  - `source manifest verify|rebuild|edit|publish <name>` finds the manifest `init` wrote for a non-GitHub URL by its bare repo name or slug (p1691).
+  - A rejected `SKAILE_GITHUB_PAT` prints one warning and the public repo is still read (p1692).
+  - `diff` labels its sides `(deployed)` and `(library)`/`(source)`/`(rendered)` instead of printing timestamps (p1693).
+  - `skaile search <word>` without a hit prints `No results for "<word>" (local and store).` (p1694).
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Upgrade: `add --global --harness X` on an asset that is already global adds X to its harness set and deploys there; the new `--only` flag replaces the set (a copy left in a harness that drops out is named, not deleted). `add --global` prints the paths it wrote, harness by harness (p1640). `check` keeps reporting a hand-edited deployed file after a library version bump, and `update` and `install` stop before they replace it, name the file and need `--force` (`update` and `install` both take it). The lock records the bytes of a copied library asset (`copied:` in `skaile.lock.yaml`) for this (p1641). A failing `install --locked` writes nothing: a library that changed since the lock or a `../` compose folder that moved leaves every restorable file as it is (p1642). `migrate assets --write` refuses a bundle or old persona/ruleset file whose final kind and name is that of a preset, ruleset or persona file the repo already holds (p1241). `check` names `skaile update` for a `../` compose folder the library changed, as `install --locked` does (p1711).
+
+### Patch Changes
+
+- [#1104](https://github.com/skaile-ai/workspaces/pull/1104) [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d) Thanks [@mortegro](https://github.com/mortegro)! - Docs: the command and protocol pages now describe what the 6.1.0 critique found wrong. `runner/api-reference.md` lists `session_init` and no longer the removed `provision_secrets` and `configure` (p1735); the flow example creates its skill in the `personal` library of tutorial 01 (p1756). Other fixes cover `files:` paths and `--description` limits in the library pages, `--project-dir` after the subcommand, library-less `install --locked`, hand-edited deployed files and `--force`, the global harness set, the default harness of a `skaile.yaml` without `agent-config`, the repl banner, stale harness copies, `validate versions` outside a library, source manifest slugs, search with no hit, the unused `secrets.timeoutMs`, local plugin specs, and the planned-only commands of the curriculum page.
+
+- Updated dependencies [[`7af33f2`](https://github.com/skaile-ai/workspaces/commit/7af33f2cf748dab42e4a5114e872ff97f55036ca), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d), [`c32d60f`](https://github.com/skaile-ai/workspaces/commit/c32d60f74f22d40d63058129f6c6b35aa3fc858d)]:
+  - @skaile/workspaces@6.2.0
+
+## 6.1.0
+
+### Minor Changes
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Agents: `install` names `skaile update` for a composed persona or ruleset the library moved past the lock (p1510). A `../` compose folder of an agent is part of the lock: only `update` moves its bytes, `outdated` lists it (p1511). `install`, `install --locked`, `check` and `doctor` refuse what `validate` rejects for `agents:` instances (p1512). `validate` warns on an unknown key inside `agent.permissions` and the `model`, `memory`, `budget` and `permissions` blocks of an instance (p634).
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Authoring: `validate`, `library index`, the publish plan and `add` give one verdict and one plain message per problem. A SKILL.md without front matter, or with front matter that is not valid YAML, prints the same `parse error` sentence everywhere, and an unquoted `@publisher/name` in `requires:` names the quoting fix (p1206, p1551). A missing `name` prints a plain fix line, once (p1401). A flow without a description is refused like every other kind (p1402). A `files:` entry outside the library is refused like `root:`, and a `files:` entry that names a missing file makes `validate`, `library index` and the plan exit 1 (p1403, p1404). `library index` drops the search rows of a library that holds no valid asset any more (p1400) and no longer tells the author to run `library index` for an asset that already fails its check (p871). `validate changelog` on a library without a commit prints a plain line (p1405). `library init --path` refuses every deploy folder below a project, including `<project>/.claude` itself (p875). `add` refuses an asset that fails its kind schema with the `validate` line, and `run --skill --dry-run` prints that line instead of a Node error (p1550). `reads_from` and `writes_to` in a flow warn like every other kind instead of failing the flow (p1552).
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Consume commands (5.19.0 critique). `outdated` lists only what `update` would change: a library registered under another name with the same remote is no `origin changes` row, and a `#pin`ned ref is shown as `pinned`, never as moving (p1420, p1455). A pin the library never held gets `change the pin in skaile.yaml` in `check`, `doctor`, `outdated` and `install --locked` (p1456). The lock's origin wins: `update` and `add` keep a store- or source-origin asset where the lock has it, and `install --locked` restores a library-origin entry from the store when the lock's library is not registered and the store serves the same hash (p1490). `update --no-catalog` keeps a locked store mcp-server like a skill (p792). `info <ref>` of a locked asset resolves against the lock's library and prints `library:` (p1445). `diff <ref>` prints a missing requirement once (p1443). `add --dry-run` prints the planned library, version, dependencies, folders and files and changes nothing (p1422). A kindless `@pub/name` works in `why` (p1424), and a kindless `add` that misses says `Did you mean agent:@pub/name?` when another kind exists (p1425).
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Harnesses: a new verb `skaile harness set <name>` switches a project to `claude-code`, `omp` or `codex` (it rewrites `agent:` and `harness:` and installs for it). `skaile init --harness` in a project that exists now refuses and names that verb. `omp` counts as logged in only when `agent.db` holds a credential, so `run --dry-run` and the real run give the same verdict. The omp ignore warning of `integration install` fires only for a rule that matches `.omp/extensions/skaile.ts` itself and names the ignore file. An unknown key of `skaile.yaml` (top level or in an `agent-config` profile) warns in `validate`, `check`, `run` and `repl`. `validate`, `check` and `doctor` reject a `harness:` or `driver:` no harness registers, after the declared plugins load. The claude-sdk surface warning is one `!` line and the SDK's stderr goes to the log database. `session logs <unknown id>` exits 1 with one line. `config set model` is judged against the project's harness and refuses a model it would refuse. `serve --harness omp --model <x>` refuses, before the ready line, a model omp would refuse: the check judges the `<entry>/<model>` the runner really sends to omp, and names it.
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - MCP servers from the store:
+
+  - A fresh `git clone` checks clean without `install`: `check` and `doctor` take the committed `.mcp.json` entry, `.skaile/assets/` payload and `.skaile/mcp-managed.json` as the render of the locked server, although `.skaile/cache/store/` is empty (p1294).
+  - `skaile remove mcp-server:<ref>` also removes an `mcp_servers:` entry of the same id that only sets values for the server, its payload and its staged store bytes (p963).
+  - `skaile diff mcp-server:<ref>` exits 1 for a missing `.mcp.json` entry, like `check` and `doctor` (p1494).
+  - `skaile store show` of an `mcp-server` this CLI writes no `.mcp.json` entry for (Nix recipe runtime, placeholder url) prints `Not runnable here: <reason>` instead of the `Install:` line (p1491). `store search` rows carry no such hint: the catalog row has no field for it.
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - `skaile serve` no longer writes into `~/.gitconfig` by default. The `[include]` of the project's managed-gitconfig is written only when `SKAILE_GIT_CONFIG_INCLUDE=1` is set (the agent image) or `startAgentServer({ gitConfigInclude: true })` is used. The write is atomic, goes through a symlinked `~/.gitconfig` and keeps its mode, and the include path is absolute. The protocol docs now agree that a default (`env` mode) runner accepts prompts without `session_init`; only a `provisioned` runner waits for `session_init_ack`.
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Sources: a GitHub-URL lock entry counts as store-supplied only when a store lists the ref; otherwise `check`, `doctor`, `outdated` and `install` print the `register it again` sentence and fail (p1062). Re-adding a ref of a source after an upstream bump re-locks every entry of that source at one commit, so `install --locked` stays clean (p21). `source add --publisher B` is refused for a source registered as A also when the clone's `origin` differs from the registered URL (p722). A library renamed and renamed back leaves no interim name in the lock or the advice (p893). `source add|list|show|sync|remove` print one parse-error line on a `skaile.yaml` that does not parse (p1421). `library list` points at `skaile source sync` for a source clone whose directory is gone (p1423). A relative, absolute, symlinked or `file://` spelling of one local repository is one source (p618). A dead `sources:` entry no longer turns a fully restored `install --locked` into `Failed`, and the warning names the cause once (p1492). `search` shows the version `add` deploys for a source skill without a version, also outside a project (p855). A `sources:` clone is project-scoped: a project that does not declare it neither searches nor resolves it (p321). The publisher-less ref error of `store show` and `add` says how to find the publisher, not the dead `migrate-skaile-manifest` advice (p1493).
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Upgrade safety (5.19.0 critique). `migrate assets --write` refuses two bundles or personas with the same final kind and normalised name (`a/q` and `b/q`, `my_b` and `my-b`) and writes nothing. `install` and `update` stop before they delete files a re-lock no longer ships (git-ignored files a CLI before 5.19.0 deployed) or overwrite a hand-edited rendered agent file no lock entry records; they name the files and need `--force` (`update` gains `--force`). `install --force` prints `Removed <file> (not part of <ref>)` for each deleted file. A 5.12.0 global record without `global_asset_harnesses:` and exactly one existing copy is limited to that harness on the first `install --global`. `library show` and `library default` refuse a registered library whose directory is gone; `library list` marks it `(directory missing)`.
+
+### Patch Changes
+
+- [#1097](https://github.com/skaile-ai/workspaces/pull/1097) [`2b6b691`](https://github.com/skaile-ai/workspaces/commit/2b6b691149300bb17360ae60e30b77b99e70cce4) Thanks [@mortegro](https://github.com/mortegro)! - A contract asset now ships its whole directory, subfolders included. The contract file filter
+  (`contractProvider.defaultFileFilter` and its virtual-tree twin) took only the files next to
+  `CONTRACT.md`, while the lock walker recorded and hashed every file under that directory: a
+  contract such as `tree/CONTRACT.md` with its nodes in `tree/01_meta/…` was locked with those files
+  but, wherever the deploy fell back to the kind's filter, installed without them, and its discovery
+  hash (library index, store, GitHub trees) differed from the lock's. Filter, deploy, lock and hash now
+  use one file set: the manifest's directory recursively, minus the non-asset names (`.DS_Store`,
+  `node_modules/`, …). A contract without subfolders keeps its files and hash.
+  A contract installed before this release with only its top-level files now reports drift until it
+  is reinstalled (`skaile install` again ships the subfolders).
+
+- [#1102](https://github.com/skaile-ai/workspaces/pull/1102) [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f) Thanks [@mortegro](https://github.com/mortegro)! - Docs for 5.19.0 findings: CURRICULUM.md teaches `skaile store search`, `store show` and `add`; `agent-config:` in every example; the `outdated` pin rule, kindless refs, the omp ignore rule, the `serve` probe routes and the instance checks are written down. The malformed-ref error of `add` and `install` now gives `skill:@skaile-ai/use-exa#1.0.0` as its example.
+
+- Updated dependencies [[`2b6b691`](https://github.com/skaile-ai/workspaces/commit/2b6b691149300bb17360ae60e30b77b99e70cce4), [`2b6b691`](https://github.com/skaile-ai/workspaces/commit/2b6b691149300bb17360ae60e30b77b99e70cce4), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f), [`196d16e`](https://github.com/skaile-ai/workspaces/commit/196d16e8e09c7ec1e8811a6d65b36ff0b3eb117f)]:
+  - @skaile/workspaces@6.1.0
+
 ## 6.0.0
 
 ### Major Changes

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "skaile-cli",
-  "version": "6.0.0",
+  "version": "6.2.0",
   "description": "Run the Skaile CLI via `npx skaile-cli` — thin wrapper around @skaile/workspaces",
   "type": "module",
   "bin": {
@@ -25,7 +25,7 @@
     "asset-manager"
   ],
   "dependencies": {
-    "@skaile/workspaces": "6.0.0"
+    "@skaile/workspaces": "6.2.0"
   },
   "publishConfig": {
     "access": "public"