Repository navigation
chore: pin opencode v1.18.10-amicode.22 - #786
aarontrowbridge wants to merge 1 commit into
Conversation
Yellow user chip (both schemes), question answers as the same chip, YOU label dropped from the sticky prompt bubble, WAAPI merge on bubble hand-offs — on the amicode.21 base (harmonic dot rail).
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Closing as superseded: the vendored pin now flips to stock canonical opencode v1.18.29 via the origin-flip slice (amicode#823 → PR #840, director-gated: 18/18 new tests + typecheck clean + CI 10/10) — not to the fork's v1.18.10-amicode.22 lineage this PR pins. The operational .22 upgrade landed on the hub mid-session 2026-09-05 (session/device-lifecycle ledger §7); the retirement-cutover path owns the shipped pin from here. (Batch-go disposition, 2026-09-06.) |
What
Lock bump: vendored fork binary
v1.18.10-amicode.18→v1.18.10-amicode.22(ref8c91b45fa8), all three platform assets sha256-verified byopencode:pin.What's in the binary (fork amico/yellow-chunks-on-21)
--accentfill +--accent-ink, ink border on light, borderless solid yellow on dark (new--prompt-bubble-edgetoken; sticky bubble included).Verification
tsgo -bclean, session-ui oxlint 0 errors