From e279790ea3e7e49710594f06ea73a784da606ea2 Mon Sep 17 00:00:00 2001 From: holo Date: Sun, 28 Jun 2026 10:53:48 +0800 Subject: [PATCH] chore(release): prepare 0.6.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cut the 0.6.4 release and bump every user-facing version reference ahead of tagging. Unlike 0.6.3 (a cadence release with `src/` untouched), 0.6.4 ships a real engine-side change: PR #246 extracted the three inline K-layer system-prompt constants (`DEFAULT_SYNTH_SYSTEM`, `_MERGE_SYSTEM`, `_GROUNDED_SYSTEM`) into packaged `prompts/*.md` and unified every packaged prompt's product self-reference from `dikw-core` to `dikw`. Constant names, call sites, on-disk format, schema, CLI, and API are all unchanged; the wheel now carries three new prompt resource files. - Version bump `0.6.3 -> 0.6.4` (`pyproject.toml` + `uv.lock` self-entry). - CHANGELOG: rename `## Unreleased` -> `## 0.6.4 — …`, open a fresh empty `## Unreleased`. The 0.6.4 heading is awk-extractable by `release.yml`'s notes extractor. - Docs/examples: bump the GHCR image tags (`docs/deployment-docker.md`), the pip-install pin (`docs/getting-started.md`), the compose `.env` default + error-message example (`examples/docker/.env.example`, `docker-compose.yml`), and the bug-report version placeholder. - `examples/docker/Dockerfile` intentionally NOT bumped — `release.yml`'s `sync-dockerfile` job auto-bumps it after the tag publishes to PyPI; its current `0.6.3` is published, so the Dockerfile guard stays green. Co-Authored-By: Claude Opus 4.8 --- .github/ISSUE_TEMPLATE/bug_report.yml | 2 +- CHANGELOG.md | 2 ++ docs/deployment-docker.md | 4 ++-- docs/getting-started.md | 2 +- examples/docker/.env.example | 2 +- examples/docker/docker-compose.yml | 2 +- pyproject.toml | 2 +- uv.lock | 2 +- 8 files changed, 10 insertions(+), 8 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index 2a2a474..77c4c83 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -34,7 +34,7 @@ body: attributes: label: Version description: Output of `dikw version`. - placeholder: "0.6.3" + placeholder: "0.6.4" validations: required: true - type: dropdown diff --git a/CHANGELOG.md b/CHANGELOG.md index cf58d57..897bc6c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,8 @@ on each entry call out exactly what shape changes break. ## Unreleased +## 0.6.4 — K-layer system prompts extracted to packaged `.md`; product self-reference unified to `dikw` + ### Changed - **K-layer system prompts extracted to `prompts/*.md`; product self-reference diff --git a/docs/deployment-docker.md b/docs/deployment-docker.md index 463c321..ea953b1 100644 --- a/docs/deployment-docker.md +++ b/docs/deployment-docker.md @@ -42,8 +42,8 @@ keeps the quick-start under a screenful. against it too: ```bash - docker run --rm -v ./base:/base ghcr.io/opendikw/dikw-core:0.6.3 init /base - docker run --rm ghcr.io/opendikw/dikw-core:0.6.3 version + docker run --rm -v ./base:/base ghcr.io/opendikw/dikw-core:0.6.4 init /base + docker run --rm ghcr.io/opendikw/dikw-core:0.6.4 version ``` There is intentionally **no floating `:latest`** — downstream pins an diff --git a/docs/getting-started.md b/docs/getting-started.md index 5d434ca..ea7dbe9 100644 --- a/docs/getting-started.md +++ b/docs/getting-started.md @@ -23,7 +23,7 @@ dikw init my-base --description "my research base" cd my-base ``` -Pin an exact version (`uv pip install 'dikw-core[postgres]==0.6.3'`) so your +Pin an exact version (`uv pip install 'dikw-core[postgres]==0.6.4'`) so your client stays on the same release as the server it talks to — `dikw client` runs a [version handshake](server.md) and hard-fails on a mismatch. diff --git a/examples/docker/.env.example b/examples/docker/.env.example index 19db01f..a416985 100644 --- a/examples/docker/.env.example +++ b/examples/docker/.env.example @@ -2,7 +2,7 @@ # released version (https://github.com/OpenDIKW/dikw-core/releases); compose # fails closed until it's set, so the debug environment never rides a stale # default. Bump deliberately when you want to debug against a newer release. -DIKW_VERSION=0.6.3 +DIKW_VERSION=0.6.4 # Required — leave blank to force compose to fail-closed until set. # Generate strong values, e.g. `openssl rand -base64 24` for both. diff --git a/examples/docker/docker-compose.yml b/examples/docker/docker-compose.yml index f7582e9..c14bec3 100644 --- a/examples/docker/docker-compose.yml +++ b/examples/docker/docker-compose.yml @@ -26,7 +26,7 @@ services: # (``docker compose up --build``); it does NOT auto-pull. Its ``args`` # forward the same DIKW_VERSION so a local build matches the pinned tag # instead of the Dockerfile's ARG default. - image: ghcr.io/opendikw/dikw-core:${DIKW_VERSION:?set DIKW_VERSION in .env to a released version, e.g. 0.6.3} + image: ghcr.io/opendikw/dikw-core:${DIKW_VERSION:?set DIKW_VERSION in .env to a released version, e.g. 0.6.4} build: context: . dockerfile: Dockerfile diff --git a/pyproject.toml b/pyproject.toml index 6dafecd..f987ef1 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -4,7 +4,7 @@ build-backend = "hatchling.build" [project] name = "dikw-core" -version = "0.6.3" +version = "0.6.4" description = "AI-native knowledge engine across the DIKW pyramid (Data → Information → Knowledge → Wisdom)" readme = "README.md" requires-python = ">=3.12" diff --git a/uv.lock b/uv.lock index 5fd7e68..bd61013 100644 --- a/uv.lock +++ b/uv.lock @@ -263,7 +263,7 @@ wheels = [ [[package]] name = "dikw-core" -version = "0.6.3" +version = "0.6.4" source = { editable = "." } dependencies = [ { name = "anthropic" },