Hotfix 0.2.1: a clean checkout of 0.2.0 cannot install

CHANGELOG.md

@@ -7,6 +7,19 @@ This file starts at 0.2.0. Everything before it is readable in the history but w
 here, and 0.1.0 shipped without a tag, so `v0.2.0` is the first release a reader can obtain by
 name.
 
+## 0.2.1 - 2026-08-13
+
+### Fixed
+
+- **`yarn install --frozen-lockfile` failed on a clean checkout of 0.2.0.** The version bump moved
+  the four packages to `0.2.0` but left `apps/web` asking for `@redrob/harness@0.1.0` and
+  `@redrob/harness` asking for `@redrob/tokenizers@0.1.0`, so yarn stopped resolving them from the
+  workspace and looked for private packages on npm. Every CI job that installs failed, while a
+  local install kept working because `node_modules` was already linked. The workspaces now depend
+  on each other by `"*"`, which resolves to the workspace whatever the version, so a future bump
+  cannot reintroduce this. `CONTRIBUTING.md` says so, and says to run a frozen-lockfile install on
+  the release branch, which is the check that would have caught it.
+
 ## 0.2.0 - 2026-08-13
 
 0.1.0 could compare models and settle quality by human preference. 0.2.0 is about what happens

CITATION.cff

@@ -12,7 +12,7 @@ authors:
   - family-names: Lee
     given-names: Janghoon
     alias: "이장훈"
-version: 0.2.0
+version: 0.2.1
 date-released: "2026-08-13"
 license: Apache-2.0
 repository-code: "https://github.com/redrob-labs/redrob-eval"

CONTRIBUTING.md

@@ -184,6 +184,15 @@ happen and the branch is just `develop` under another name.
 in the root, `apps/web`, `packages/harness` and `packages/tokenizers` `package.json`, plus
 `version:` in `CITATION.cff`.
 
+Those five are the whole list because the workspaces depend on each other by `"*"` rather than by
+an exact version. Do not pin them: 0.2.0 shipped with `@redrob/harness` still asked for at
+`0.1.0`, so `yarn install --frozen-lockfile` looked for a private package on npm and every CI job
+failed, while a local install kept working because `node_modules` was already linked. Nothing here
+is published, so an exact internal pin only adds a second place to remember.
+
+**Run `yarn install --frozen-lockfile` on the release branch** before merging, in a clean checkout
+rather than in your working tree. It is the one check that sees a version bump the way CI does.
+
 **QA happens in three layers, and only the first two are automated.**
 
 1. *Every pull request into `develop`* runs both workflows: typecheck, lint, the `verify:*`

apps/web/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@redrob/web",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "private": true,
   "license": "Apache-2.0",
   "author": "Janghoon Lee",
@@ -11,7 +11,7 @@
     "lint": "eslint"
   },
   "dependencies": {
-    "@redrob/harness": "0.1.0",
+    "@redrob/harness": "*",
     "@xterm/addon-fit": "^0.10",
     "@xterm/xterm": "^5",
     "clsx": "2.1.1",

package.json

@@ -1,6 +1,6 @@
 {
   "name": "redrob-eval",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "private": true,
   "license": "Apache-2.0",
   "author": "Janghoon Lee",

packages/harness/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@redrob/harness",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "private": true,
   "license": "Apache-2.0",
   "author": "Janghoon Lee",
@@ -15,7 +15,7 @@
     "typecheck": "tsc -p tsconfig.json --noEmit"
   },
   "dependencies": {
-    "@redrob/tokenizers": "0.1.0"
+    "@redrob/tokenizers": "*"
   },
   "devDependencies": {
     "@types/node": "^20",

packages/tokenizers/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@redrob/tokenizers",
-  "version": "0.2.0",
+  "version": "0.2.1",
   "private": true,
   "license": "Apache-2.0",
   "author": "Janghoon Lee",