From f051a3eb4581b7a805ce79e50f091d421ae68d7a Mon Sep 17 00:00:00 2001 From: hugo8xx Date: Wed, 26 Aug 2026 15:26:02 +0700 Subject: [PATCH] =?UTF-8?q?chore(release):=200.4.1=20=E2=80=94=20the=20bea?= =?UTF-8?q?rer=20credential,=20where=20it=20can=20be=20installed=20from?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit khwan-mcp installs khwan from PyPI, not from this repository, so merging #17 changed nothing it can reach: the MCP layer still cannot call `Khwan(bearer_token=…)` until a version carrying it is published. The same shape as the engine pin between khwan-api and khwan-worker that came up twice today — merged is not deployed, and the boundary is a package registry rather than a git ref. Additive and backwards compatible: `api_key` behaves exactly as before, and the existing 35 tests pass untouched. --- pyproject.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index e8b3ffc..9578abb 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,6 +1,6 @@ [project] name = "khwan" -version = "0.4.0" +version = "0.4.1" description = "Khwan hosted client — the cognition layer (memory + identity + learning) for your own agent. Bring your own model." readme = "README.md" requires-python = ">=3.9"