bug: eval CLI --version reports hardcoded 0.1.0 instead of package.json version #95

New Issue

2026-06-05T06:37:51Z

xiaoju commented

2026-06-05 06:37:51 +00:00

What

uwf-eval --version always reports 0.1.0 regardless of the actual published version.

Root Cause

packages/eval/src/cli.ts:15 hardcodes .version("0.1.0") instead of reading from package.json like the main CLI does.

// eval/src/cli.ts:15 — BAD
.version("0.1.0");

// cli/src/cli.ts:58 — GOOD
.version(pkg.default.version, "-V, --version");

Expected

uwf-eval --version should report the version from package.json (currently 0.1.2).

Fix

Read version from package.json at runtime, same pattern as packages/cli/src/cli.ts.

— 小橘 🍊（NEKO Team）

## What `uwf-eval --version` always reports `0.1.0` regardless of the actual published version. ## Root Cause `packages/eval/src/cli.ts:15` hardcodes `.version("0.1.0")` instead of reading from `package.json` like the main CLI does. ```typescript // eval/src/cli.ts:15 — BAD .version("0.1.0"); // cli/src/cli.ts:58 — GOOD .version(pkg.default.version, "-V, --version"); ``` ## Expected `uwf-eval --version` should report the version from `package.json` (currently `0.1.2`). ## Fix Read version from `package.json` at runtime, same pattern as `packages/cli/src/cli.ts`. — 小橘 🍊（NEKO Team）

xiaoju referenced this issue from a commit

2026-06-05 06:46:09 +00:00

fix: read eval CLI version from package.json

xiaoju referenced a pull request that will close this issue

2026-06-05 06:46:26 +00:00

fix: read eval CLI version from package.json #96

xiaoju closed this issue

2026-06-05 06:46:33 +00:00

xiaoju referenced a pull request that will close this issue

2026-06-05 07:32:25 +00:00

fix: add --version to adapter CLIs, read VERSION from package.json #97

Sign in to join this conversation.