From 463491136a67b612f0e1caf5970c2d038b7828ed Mon Sep 17 00:00:00 2001
From: Muhammad Zakir Ramadhan <61570975+zakirkun@users.noreply.github.com>
Date: Thu, 3 Sep 2026 01:47:37 +0700
Subject: [PATCH] release 0.1.0-beta.2

Bump src/version.ts and package.json together; release.ts refuses to build if
they disagree, or if the git tag disagrees with either.

Also updates the version shown in the README and MCP sample headers, and the
example in development.md so it points at the next release rather than this one.
---
 README.md           | 2 +-
 ROADMAP.md          | 2 +-
 docs/development.md | 6 +++---
 docs/mcp.md         | 2 +-
 package.json        | 2 +-
 src/version.ts      | 2 +-
 6 files changed, 8 insertions(+), 8 deletions(-)

diff --git a/README.md b/README.md
index 4196079..5a4841f 100644
--- a/README.md
+++ b/README.md
@@ -46,7 +46,7 @@ from the models that endpoint actually reports. Settings land in
 `~/.shiro-neko/config.json`. Run `/provider` any time to change them.
 
 ```
-shiro-neko 0.1.0-beta.1  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.2  openai/gpt-5  session 0193ab2c
 agent: default  thinking: medium
 cwd: /home/you/project
 skills: debug, refactor, review, test
diff --git a/ROADMAP.md b/ROADMAP.md
index 9dcda6d..cebfad5 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -49,7 +49,7 @@ reported rather than fatal.
 **Distribution** — five-platform cross-compiled binaries, checksums, install scripts, CI on
 three operating systems, tag-driven releases.
 
-### 0.1.0-beta.2 (unreleased)
+### 0.1.0-beta.2
 
 Fourteen built-in tools, up from six, with sets so the schema cost stays controllable.
 
diff --git a/docs/development.md b/docs/development.md
index a37c4f2..fcdb50c 100644
--- a/docs/development.md
+++ b/docs/development.md
@@ -124,7 +124,7 @@ disagrees with either:
 
 ```
 $ GITHUB_REF_NAME=v9.9.9 bun run release
-tag v9.9.9 does not match src/version.ts (0.1.0-beta.1). Bump the version or retag.
+tag v9.9.9 does not match src/version.ts (0.1.0-beta.2). Bump the version or retag.
 ```
 
 A binary reporting the wrong version is worse than a failed release.
@@ -133,8 +133,8 @@ To cut one:
 
 ```bash
 # bump src/version.ts and package.json to the same value
-git commit -am "release 0.1.0-beta.2"
-git tag v0.1.0-beta.2
+git commit -am "release 0.1.0-beta.3"
+git tag v0.1.0-beta.3
 git push --follow-tags
 ```
 
diff --git a/docs/mcp.md b/docs/mcp.md
index 4b54815..b558ed3 100644
--- a/docs/mcp.md
+++ b/docs/mcp.md
@@ -54,7 +54,7 @@ one tool for the session.
 A server that fails to start is reported and the session continues:
 
 ```
-shiro-neko 0.1.0-beta.1  openai/gpt-5  session 0193ab2c
+shiro-neko 0.1.0-beta.2  openai/gpt-5  session 0193ab2c
 mcp: 4 tools
 mcp db failed: spawn python ENOENT
 ```
diff --git a/package.json b/package.json
index 7f2704f..e8f333a 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "shiro-neko",
-  "version": "0.1.0-beta.1",
+  "version": "0.1.0-beta.2",
   "type": "module",
   "private": true,
   "bin": {
diff --git a/src/version.ts b/src/version.ts
index 0c0457d..fea0380 100644
--- a/src/version.ts
+++ b/src/version.ts
@@ -5,7 +5,7 @@
  * fails inside the shipped binary. A constant is compiled in and always correct.
  * `scripts/release.ts` checks it against the release tag so the two cannot drift.
  */
-export const VERSION = '0.1.0-beta.1';
+export const VERSION = '0.1.0-beta.2';
 
 /** What `--version` prints: enough to identify a build from a bug report. */
 export function versionLine(): string {