Repository navigation
v0.8.2
·
514 commits
to main
since this release
Immutable
release. Only release title and notes can be modified.
caret 0.8.2 fixes an install-breaking bug that has shipped since 0.5.0 — every bundled install served the daemon's "UI not built yet" placeholder instead of the review UI — and gives caret install a real upgrade path, where --refresh brings a stale OpenCode or Claude Code install current. It also redraws caret-dark and caret-light as a named earth-pigment color set, with syntax themes authored to match rather than derived from the UI palette.
Added
caret install --refreshchecks whether the caret each agent would load is behind the published one, and updates it: clearing a stale OpenCode plugin cache or bumping a stale version pin, and runningplugin updatefor Claude Code. Without the flag the check prompts; off a terminal it names the gap and the command and changes nothing.- caret-dark and caret-light get shiki themes of their own, authored rather than derived. Eleven syntax-only hues separate types from functions, numbers from escapes, and attributes from properties — distinctions the derivation had no colors to draw.
Changed
- caret-dark and caret-light are redesigned as a named 27-color set in an earth-pigment direction. Dark mode's page is a kraft brown rather than a neutral near-black, its rules ride bone instead of pure white, and the accent is a designed carrot-top. Both schemes pull further from their ink than before, and every hue clears its contrast floor on the surfaces it sits on.
- Install and uninstall sweep caret's pre-array-install OpenCode artifacts — the file-deploy-era plugin file in both
plugins/andplugin/, plus thecaret:-namespaced command files incommand/. OpenCode scans both spellings, so a leftover plugin file registered a secondcaret_review_planbeside the array entry. caret install --from-localwrites afile:entry pointing at the checkout for OpenCode, so a local build is the copy OpenCode actually loads. It previously wrote the npm specifier, and a bare specifier resolves once and never re-resolves — so OpenCode kept loading whatever its cache held, potentially many releases old.- The README and
doc/ADVANCED.mdupdate instructions point atcaret install --refresh. The old ones said to delete a cache path caret has never written, which made the documented update a silent no-op.
Fixed
- Bundled installs served the daemon's "UI not built yet" placeholder instead of the review UI. The bundle collapses to a single output file, so the one candidate path for
ui/distovershot the package root by a level and no on-disk tree resolved. Every npm and GitHub install since 0.5.0 was affected. - A
caret reviewthat loses its connection attaches to the running daemon instead of taking the port over. A client whose review outlived an upgrade is running the old build, so every dropped poll reinstated that build's daemon — and reconnects outpace rebuilds, so it won indefinitely. - The OpenCode discovery probe reported every healthy install as not-installed. It read
opencode/node_modules/<pkg>, a path OpenCode never writes; it now resolves the realpackages/<specifier>/layout and reads the version from that directory's manifest.