From be9465eed519572dfcece9322193a1dba7a34f46 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Tue, 4 Aug 2026 19:54:24 +0000
Subject: [PATCH] Version Packages

---
 .changeset/kontena-entry-slug-lookup.md | 8 --------
 packages/sawala-mcp/CHANGELOG.md        | 8 ++++++++
 packages/sawala-mcp/package.json        | 2 +-
 packages/sawala/CHANGELOG.md            | 8 ++++++++
 packages/sawala/package.json            | 2 +-
 5 files changed, 18 insertions(+), 10 deletions(-)
 delete mode 100644 .changeset/kontena-entry-slug-lookup.md

diff --git a/.changeset/kontena-entry-slug-lookup.md b/.changeset/kontena-entry-slug-lookup.md
deleted file mode 100644
index de598d5..0000000
--- a/.changeset/kontena-entry-slug-lookup.md
+++ /dev/null
@@ -1,8 +0,0 @@
----
-"@sawala/cli": patch
-"@sawala/mcp": patch
----
-
-`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`.
diff --git a/packages/sawala-mcp/CHANGELOG.md b/packages/sawala-mcp/CHANGELOG.md
index 48e969d..23e3332 100644
--- a/packages/sawala-mcp/CHANGELOG.md
+++ b/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
diff --git a/packages/sawala-mcp/package.json b/packages/sawala-mcp/package.json
index abe60c4..e213b54 100644
--- a/packages/sawala-mcp/package.json
+++ b/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": {
diff --git a/packages/sawala/CHANGELOG.md b/packages/sawala/CHANGELOG.md
index 457f9a6..95bbdd1 100644
--- a/packages/sawala/CHANGELOG.md
+++ b/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
diff --git a/packages/sawala/package.json b/packages/sawala/package.json
index 179f2b9..8595ea8 100644
--- a/packages/sawala/package.json
+++ b/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": {