v0.1.26 — one visual system across Settings, home and the project directory - #68
Merged
Conversation
Bump the display, Cargo, Tauri, capability manifest and Codex plugin versions to 0.1.26 and add the reviewed release-note catalog entry in all five shipped locales. Two assertions in `scripts/release-notes.test.ts` are made self-deriving rather than re-pinned. They encoded the shipping version's own content — the catalog's version list and the English highlight titles — so every release edited this file to restate what it had just written. The head now derives from `package.json` and the render assertions iterate the catalog entry itself, so the test checks that the CLI carries the catalog's copy rather than a snapshot of one release's copy. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`version.replace(/\./g, '\\.')` escapes dots but leaves backslashes alone, which CodeQL flags as incomplete sanitization — the same mistake made hours earlier in `commerce-operator.test.ts` and fixed there by dropping the regex entirely. It came back because the fix was applied to one call site instead of to the habit. This assertion never needed a sanitizer. It needs the literal shape the renderer emits (`Cutout v0\.1\.26`, dots markdown-escaped), so split/join produces it directly. A sweep for the same pattern across src, scripts and tests finds no other instance. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What ships
The four-surface visual unification merged in #67, plus the fixes found while verifying it against a real install.
MOX · gpt-image-2) instead of a bare model id, and an unassigned task states which task it inherits from instead of showing a bare "Auto".{0}while the source names it{catalogSize}, so the number came out empty — it shipped in v0.1.25 and was caught from a user screenshot, not from CI. A catalog parity test now fails on that class of mismatch.Release mechanics
Version bumped across display, Cargo, Tauri, the capability manifest and the Codex plugin; reviewed release notes added in all five shipped locales.
Two assertions in
scripts/release-notes.test.tsare made self-deriving rather than re-pinned. They encoded the shipping version's own content — the catalog version list and the English highlight titles — so every release edited this file to restate what it had just written. The head now derives frompackage.jsonand the render assertions iterate the catalog entry itself. Same guarantee, no per-release edit.Verification
pnpm lint·tsc --noEmit -p tsconfig.app.json· 464 vitest suites · 136 Playwright visual tests ·pnpm build· 322 Rust tests ·release-notes:validate --require-all-locales·validate-release-version --expected 0.1.26— all pass.🤖 Generated with Claude Code