v0.6.4
Release v0.6.4
Date: 2026-08-07
Summary
- Blast-radius reports now upload to LiveReview over a new generic artifact-sync channel, and the review UI header gets a persistent status chip showing upload progress, size, and transfer time.
Install and Update
New install:
# Linux/macOS
curl -L https://hexmos.com/ipm-install | bash && ipm i HexmosTech/git-lrc
# Windows
iwr https://hexmos.com/ipm-install-ps | iex; ipm i HexmosTech/git-lrc
Update:
lrc self-update
Changes
- Added a generic artifact-sync channel to LiveReview (
network.ReviewUploadArtifact,POST /api/v1/diff-review/{review_id}/artifacts/{artifact_type}) and wired the blast-radius report through it as the first consumer (internal/appcore/blastradius_bridge.go). Upload is fire-and-forget and non-fatal on failure, matching how blast-radius scoring already treats its own errors. - Replaced the transient blast-radius upload banner with a persistent "Blast Radius" status chip in the review UI header (
internal/staticserve/static/components/Header.js), styled after the existing usage chip. It tracks idle/uploading/uploaded/failed state and shows report size and transfer time on hover. - Tracked upload size (
size_bytes) and duration (duration_ms) alongside the existing status/error fields on the blast-radius upload state. - Documented the LiveReview sync convention in
AGENTS.md("Rule 4: Syncing to LiveReview") so future changes toblastradius/or the review UI flag when a ported copy in the LiveReview repo may need a follow-up update. - Fixed stale evidence line references in
network/network_status.mdafter the newReviewUploadArtifactfunction shifted the line numbers ofReviewProxyRequestandReviewForwardJSONWithBearer.
Breaking Changes
- None.
Verification
- lrc --version
- lrc --help
Known Issues
- None.