Version Packages

packages/sawala-mcp/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @sawala/mcp
 
+## 0.4.1
+
+### Patch Changes
+
+- 917500d: `sawala kontena entry create/update/delete` and the matching `sawala_kontena_create_entry`, `sawala_kontena_update_entry` and `sawala_kontena_delete_entry` MCP tools now work when you name the schema by its slug — previously they failed with `NOT_FOUND (…/schemas/<slug>)` for every schema.
+
+  The commands look the schema up first to decide whether to write to the `single` or the `collection` content route, and that lookup only resolves a schema's ULID. The content route it feeds only resolves the schema's _slug_, so the identifier that made the write succeed was exactly the one that made the lookup fail, and there was no value that worked for both. The lookup now falls back to listing the project's schemas and matching by slug, the same way `sawala kontena schema get` already did. When the schema really is absent you get `Schema 'x' not found. Available slugs: …` instead of a bare `NOT_FOUND`.
+
 ## 0.4.0
 
 ### Minor Changes

packages/sawala-mcp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sawala/mcp",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "description": "Drive the Sawala API (Kontena, Formulir, Berkasna, Kodena) from any MCP-capable AI agent.",
   "license": "MIT",
   "repository": {

packages/sawala/CHANGELOG.md

@@ -1,5 +1,13 @@
 # @sawala/cli
 
+## 0.14.2
+
+### Patch Changes
+
+- 917500d: `sawala kontena entry create/update/delete` and the matching `sawala_kontena_create_entry`, `sawala_kontena_update_entry` and `sawala_kontena_delete_entry` MCP tools now work when you name the schema by its slug — previously they failed with `NOT_FOUND (…/schemas/<slug>)` for every schema.
+
+  The commands look the schema up first to decide whether to write to the `single` or the `collection` content route, and that lookup only resolves a schema's ULID. The content route it feeds only resolves the schema's _slug_, so the identifier that made the write succeed was exactly the one that made the lookup fail, and there was no value that worked for both. The lookup now falls back to listing the project's schemas and matching by slug, the same way `sawala kontena schema get` already did. When the schema really is absent you get `Schema 'x' not found. Available slugs: …` instead of a bare `NOT_FOUND`.
+
 ## 0.14.1
 
 ### Patch Changes

packages/sawala/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sawala/cli",
-  "version": "0.14.1",
+  "version": "0.14.2",
   "description": "Sawala umbrella CLI — Kontena, Formulir, Berkasna, and Kodena under one roof.",
   "license": "MIT",
   "repository": {