[Bug]: Binary --version outputs 3.11.0 instead of 3.11.2 in v3.11.2 release

[EightDoor]

Prerequisites

• I will write this issue in English (see our Language Policy)
• I have searched existing issues to avoid duplicates
• I am using the latest version of oh-my-opencode
• I have read the documentation or asked an AI coding agent with this project's GitHub URL loaded and couldn't find the answer

Bug Description

The --version flag outputs 3.11.0 even though the installed version is 3.11.2.

Steps to Reproduce

Bug Description

The --version flag outputs 3.11.0 even though the installed version is 3.11.2.

Steps to Reproduce

1. Install oh-my-opencode v3.11.2 via bun:

   bun update -g oh-my-opencode

2. Check the package.json versions (both show 3.11.2):
   cat ~/.bun/install/global/node_modules/oh-my-opencode/package.json | grep version
   cat ~/.bun/install/global/node_modules/oh-my-opencode-darwin-arm64/package.json | grep version

3. Run the binary with --version:
   ~/.bun/install/global/node_modules/oh-my-opencode-darwin-arm64/bin/oh-my-opencode --version

   Output: 3.11.0 <-- Expected: 3.11.2

Expected Behavior
--version should output 3.11.2.
Actual Behavior
--version outputs 3.11.0.
Environment

• OS: macOS (darwin-arm64)
• Install method: bun global install
  Analysis
  The version string embedded in the compiled binary was not updated when releasing v3.11.2. Package.json files are correct, but the binary's internal version string is out of sync.

Expected Behavior

The version is displayed correctly

Actual Behavior

Inconsistent version number

Doctor Output

- OS: macOS (darwin-arm64)
- Install method: bun global install

Error Logs

Configuration

Additional Context

No response

Operating System

macOS

OpenCode Version

3.11.0

[acamq]

Update your bun.lock file and delete the node_modules directory in ~/.cache/opencode

[8-unlimit]

I have the same problem

[godfwy]

I can confirm this issue on Windows as well.

Environment:

• OS: Windows 11 Pro (10.0.26200)
• Install method: npm global install (also tested with bun)
• Node version: v24.13.0 (managed by fnm)

Steps I took:

1. Installed via npm: npm install -g oh-my-opencode@3.11.2
2. Verified package.json shows version 3.11.2:

   type "C:\Users\F\AppData\Roaming\npm\node_modules\oh-my-opencode\package.json" | findstr version
   "version": "3.11.2"
   

3. Running oh-my-opencode --version outputs: 3.11.0

Also tested with bun global install - same result.

Additional findings:

• npm view oh-my-opencode@3.11.2 version confirms the registry has 3.11.2
• The package.json in the installed directory correctly shows 3.11.2
• The binary/executable still reports 3.11.0

This confirms the issue is cross-platform (macOS and Windows) and affects multiple install methods (npm, bun). The version string appears to be hardcoded in the compiled binary rather than being read from package.json at runtime.

I tried the suggested workaround (clearing cache and reinstalling) but the issue persists on Windows.

[gao972609504]

同样的问题

[acamq]

@gao972609504 Thank you for reporting, and please follow the language policy.

[acamq]

Root Cause: The "Git commit and tag" step was removed from publish.yml when adding oh-my-openagent dual-publish support. This caused:

1. Version bumps were applied in-memory but never committed to git
2. publish-platform.yml does a fresh checkout, getting the old version from package.json
3. bun build --compile embeds the version at compile time from root package.json

The actual source code compiled was correct — only the version string was stale.

---

Fixes Applied

File	Fix
publish.yml	Restored "Git commit and tag" step to commit version bumps
publish-platform.yml	Added defensive update of root package.json before building

The next release will have the correct version embedded.