chore(release): v0.12.4
Issue for this PR
Release PR — no issue. Promotes the v0.12.3..main payload to latest as v0.12.4: #1365, #1366, #1371, #1373, #1374, #1375, #1376, #1377. #1381 (workspaces on by default) is deliberately not included.
Type of change
- Other: release
What does this PR do?
Two commits on top of main (93fe816e20):
fix(workspace): v0.12.4 release review— fixes from this release's five-persona review.release: v0.12.4— the CHANGELOG entry andrelease-v0.12.4-adversarial.test.ts.
Review consensus: CTO SHIP; PM, End User and Tech Lead SHIP WITH NOTES; Chaos Gremlin (this release: privacy & data-governance officer) HOLD on one P0, since downgraded.
- P0, downgraded as intended behaviour: the live memory mirror uploads new memory to a workspace link the client discovered on the server (
adopted), without asking. A project belongs to exactly one workspace, so memory saved in a linked project belongs to that workspace; #1373's consent gate covers the separate case of backfilling memory saved before the link was found, and that still asks. The comment instate.tsthat described this as an unfixed gap — which is what raised the P0 — is corrected so it stops tripping future reviews. - P2 (End User), fixed: five user-facing link / re-link messages said "binding" or "pre-check".
- P2 (Tech Lead), fixed: import spacing in
identity.ts. - P1 (PM), checked and closed: skill discovery now runs one
realpathper skill file for every user (#1377). A skill whose path cannot be resolved is left out, which is what already happened to a skill behind a broken symlink (checked against the built binary). Listed under Known limitations; the fast path is #1382. - P1 (Tech Lead), checked and closed: CI on
mainat 93fe816e20 is red ondbt-tools E2E(theuvscenario) — the same job failed on the v0.12.3 release commit and is tracked in #1257 — and on analtimate-coderun triggered by an issue comment, not by a push.
Which changes reach users outside the pilot: #1365 (the TUI model-store copy), the per-skill realpath above, and link / skill publish printing a pilot-off message instead of "Failed to change directory to …/link" (with --workspace hidden from --help). Everything else is behind ALTIMATE_WORKSPACE=1.
Deferred and filed: #1382 (realpath fast path), #1383 (an unexplained one-off workspace test failure), #1384 ("datamate" in a serve error, pre-existing), #1385 (confirm the IDE extension calls the new serve routes from its host process — a webview fetch would be refused by the origin gate), #1386 (MCP tests read the developer's real ~/.claude.json). Waived: documenting the /altimate/* routes in docs/develop/server.md, as they are internal to the extension. #1377 also fixes #1339, which will be closed with the release.
How did you verify your code works?
bun script/release-preflight.ts --version 0.12.4—preandtagstages: 9 PASS, 0 WARN, 0 FAILbun turbo typecheck: 13/13 packagesscript/upstream/analyze.ts --markers --base origin/main --strict: cleanrelease-v0.12.4-adversarial.test.ts(31 tests) plus the workspace suites touched by the review fixes: 153 pass, 0 failOPENCODE_VERSION=0.12.4 bun run pre-release: all checks passed; the dist binary reports exactly0.12.4- Full
packages/opencodesuite on this branch: 14,333 pass, 780 skip, 6 fail. All 6 are MCP tests that read the machine's real~/.claude.json; they fail identically onmainand pass (15/15) withHOMEpointed at an empty directory — filed as #1386, not release code
Screenshots / recordings
N/A — CLI/TUI text and docs only.
Checklist
- I have tested my changes locally
- I have not included unrelated changes in this PR
🤖 Generated with Claude Code
https://claude.ai/code/session_018fJ3X7pcGT4R9yzjsJnqsV
Summary by cubic
Promotes the v0.12.3..main payload to latest as v0.12.4: one fix for every TUI user and the next workspace-pilot batch, all still behind ALTIMATE_WORKSPACE=1. Workspaces being on by default is deliberately excluded.
Workspace pilot
serveexposes/workspaceRefresh/Sync andskill publishfor the IDE extension, with a browser-origin gate (409 outside the pilot).- A sync now lists skipped skills (at most three, with plain reasons); an offline check on a linked project warns instead of passing silently.
- Linking asks before backfilling memory saved earlier; new memory in a linked project still goes to its workspace.
- Workspace state (cached link, snapshot, resolver caches) is keyed on the account, so two Altimate accounts on one machine no longer share it.
- The cache format changed: after upgrading, each project's cached link and synced skills are re-fetched on first use.
- Snapshot attribution now returns the platform root for a project opened at a filesystem root (
C:\, UNC share) instead of the bare drive; no user could hit this, it hardens future callers.
Fixes
- Returning to a TUI conversation keeps the model it was using.
- Link and re-link messages no longer say "binding" or "pre-check"; a missing link now names both possible causes (workspace or project link gone, or access lost) instead of telling an attach user to "pick Create".
Summary by CodeRabbit
- New Features
- Pilot workspaces support HTTP routes for syncing, IDE skill publishing, and warnings about skipped skills or offline sync.
- Linking a workspace prompts for confirmation before uploading previously saved memory. Newly saved memory continues syncing to adopted workspaces.
- Workspace links, cached data, and synced skills are scoped to the signed-in account; snapshots without attributable workspace ownership are withheld.
- Bug Fixes
- Fixed model retention when returning to a TUI conversation.
- Clarified workspace menu, linking, access, and pilot-disabled command messages.
- Known Limitations
- Skill path resolution and filename-only secret filtering have limitations. Cache format upgrades may affect existing cached data.