release 0.1.0-beta.3

v0.1.0-beta.2 was tagged but never published: the release workflow failed on the
windows-x64 build, so no release object and no artifacts exist under that tag.
The fix is in df5f9f8. Burning the version is cheaper than moving a tag that is
already on the remote.

ROADMAP records what happened, and development.md now says plainly that a green
local `bun run release` is not proof — the Windows host takes a different branch
from the Ubuntu runner CI releases from.
This commit is contained in:
Muhammad Zakir Ramadhan
2026-09-03 02:05:15 +07:00
parent df5f9f83fd
commit 8b1895de98
6 changed files with 18 additions and 8 deletions
+1 -1
View File
@@ -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.2 openai/gpt-5 session 0193ab2c
shiro-neko 0.1.0-beta.3 openai/gpt-5 session 0193ab2c
mcp: 4 tools
mcp db failed: spawn python ENOENT
```