From 170b3d69c5aa378087b516cec41a48936694884b Mon Sep 17 00:00:00 2001 From: ori Date: Tue, 13 Oct 2026 23:33:25 +0300 Subject: [PATCH 1/2] chore: prepare v0.19.2 release Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 5 ++++- CONTRIBUTING.md | 8 ++++---- README.md | 14 +++++++------- docs/opencode-v2-poc.md | 6 +++--- package.json | 2 +- src/version.ts | 2 +- 6 files changed, 20 insertions(+), 17 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 61de506..8c10684 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,6 +8,8 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Version ## [Unreleased] +## [0.19.2] — 2026-10-13 + ### Added - Added separate PR CI guards via `just test-int` for harness integration and `just test-e2e` for cache-installed OpenCode v1/v2 E2E editing, with exact prompt checks and no-plugin controls; local runs remain on demand and outside the unit suite. @@ -393,7 +395,8 @@ First release. Modal editing for the OpenCode prompt. > `g` fires immediately as buffer-home instead of waiting for `gg`. The `yy` line tracker drifts on clicks and arrow keys. Visual mode and text objects aren't feasible without cursor position access. -[Unreleased]: https://github.com/oribarilan/vimcode/compare/v0.19.1...HEAD +[Unreleased]: https://github.com/oribarilan/vimcode/compare/v0.19.2...HEAD +[0.19.2]: https://github.com/oribarilan/vimcode/compare/v0.19.1...v0.19.2 [0.19.1]: https://github.com/oribarilan/vimcode/compare/v0.19.0...v0.19.1 [0.19.0]: https://github.com/oribarilan/vimcode/compare/v0.18.1...v0.19.0 [0.18.1]: https://github.com/oribarilan/vimcode/compare/v0.18.0...v0.18.1 diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 0d7a34d..c41ca0a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -65,7 +65,7 @@ Follow [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Add your change ## Host support policy -OpenCode v2 support is rolling out gradually and remains experimental in vimcode v0.19.1. Future maintenance will move to v2 only; v1 compatibility remains in this release. The recommended v1 pin stays at `v0.18.1`. Do not automatically advance that legacy recommendation when preparing a v2-focused release. +OpenCode v2 support is rolling out gradually and remains experimental in vimcode v0.19.2. Future maintenance will move to v2 only; v1 compatibility remains in this release. The recommended v1 pin stays at `v0.18.1`. Do not automatically advance that legacy recommendation when preparing a v2-focused release. ## Release process @@ -88,19 +88,19 @@ Releases are manual. Both host versions load the same `./tui` package entry via a Git URL. Pin a tag or commit so upgrades use a new cache entry. -On OpenCode **v1**, use `tui.json`. The recommended legacy pin is `v0.18.1`; `v0.19.1` includes v1 compatibility and the subagent-navigation fix for users who opt in: +On OpenCode **v1**, use `tui.json`. The recommended legacy pin is `v0.18.1`; `v0.19.2` includes v1 compatibility plus the subagent-navigation and question-answer fixes for users who opt in: ```json { "plugin": ["vimcode@git+https://github.com/oribarilan/vimcode.git#v0.18.1"] } ``` -On OpenCode **v2**, use `cli.json` and pin `v0.19.1`. v2 support is experimental; the v1-only `v0.18.1` release does not work on v2: +On OpenCode **v2**, use `cli.json` and pin `v0.19.2`. v2 support is experimental; the v1-only `v0.18.1` release does not work on v2: ```json { "plugins": [ { - "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.1" + "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.2" } ] } diff --git a/README.md b/README.md index 5215a35..ca8917c 100644 --- a/README.md +++ b/README.md @@ -27,8 +27,8 @@ OpenCode v2 support is rolling out gradually, starting with experimental support | OpenCode version | Recommended vimcode pin | Status | |------------------|-------------------------|--------| -| v1 | `v0.18.1` | Previous v1-only release. Opt into `v0.19.1` for the subagent-navigation fix and shared v1/v2 updates. | -| v2 | `v0.19.1` | Experimental; validated on OpenCode 2.0.15 on macOS. | +| v1 | `v0.18.1` | Previous v1-only release. Opt into `v0.19.2` for the subagent-navigation and question-answer fixes plus shared v1/v2 updates. | +| v2 | `v0.19.2` | Experimental; validated on OpenCode 2.0.15 on macOS. | V1 users can stay on an older pinned release instead of following the v2 rollout. We have not set a date for removing v1 support. @@ -38,7 +38,7 @@ Use the instructions for your OpenCode major version. Both versions use the same ### OpenCode v1 -We recommend pinning `v0.18.1` for existing v1 users who want the previous v1-only behavior. To get the subagent-navigation fix and shared updates in `v0.19.1`, change the Git ref to `v0.19.1`; revert to the older pin if you encounter a regression. +We recommend pinning `v0.18.1` for existing v1 users who want the previous v1-only behavior. To get the subagent-navigation and question-answer fixes plus shared updates in `v0.19.2`, change the Git ref to `v0.19.2`; revert to the older pin if you encounter a regression. Add to your `tui.json` (or `.opencode/tui.json`): @@ -54,13 +54,13 @@ By default, you'll see a toast when a newer vimcode version is available. If you ### OpenCode v2 (experimental) -Pin `v0.19.1` in your global `cli.json`. The older `v0.18.1` release does **not** support v2. +Pin `v0.19.2` in your global `cli.json`. The older `v0.18.1` release does **not** support v2. ```json { "plugins": [ { - "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.1" + "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.2" } ] } @@ -88,7 +88,7 @@ Put `options` alongside `package` in `cli.json`: { "plugins": [ { - "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.1", + "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.2", "options": { "updateCheck": false } } ] @@ -157,7 +157,7 @@ On **v2**, set both the host keybind and the plugin option in `cli.json`: "keybinds": { "leader": "space" }, "plugins": [ { - "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.1", + "package": "vimcode@git+https://github.com/oribarilan/vimcode.git#v0.19.2", "options": { "experimentalV2Leader": "space" } } ] diff --git a/docs/opencode-v2-poc.md b/docs/opencode-v2-poc.md index 0b3f417..143e412 100644 --- a/docs/opencode-v2-poc.md +++ b/docs/opencode-v2-poc.md @@ -1,6 +1,6 @@ # Experimental OpenCode v2 POC -These notes record the v2 proof of concept and compatibility evidence. v2 support is experimental in vimcode v0.19.1; this is not a full-parity or all-versions support declaration. The same `./tui` entry has v1 `tui(api, options)` and v2 `setup(context)` callbacks. v1 still uses its existing API; v2 adapts the host UI, storage, commands and events to the same Vim controller and engine. +These notes record the v2 proof of concept and compatibility evidence. v2 support is experimental in vimcode v0.19.2; this is not a full-parity or all-versions support declaration. The same `./tui` entry has v1 `tui(api, options)` and v2 `setup(context)` callbacks. v1 still uses its existing API; v2 adapts the host UI, storage, commands and events to the same Vim controller and engine. ## Local development @@ -23,7 +23,7 @@ The root `tui.ts` re-exports `src/index.ts` for v2's local-directory loader. Thi The v2 public `keymap` has no key intercept or configured-leader lookup. The POC uses `context.renderer.keyInput.prependListener("keypress", ...)` to intercept prompt keys **before** the host keymap. It calls both `preventDefault()` and `stopPropagation()` on consumed keys. This raw OpenTUI ordering is not a documented OpenCode plugin guarantee; do not rely on it as production compatibility without testing against installed packages and future host releases. -The [README](../README.md#opencode-v2-experimental) shows the release Git install pinned to `v0.19.1`. The earlier Git experiment below used commit `d8050f765b6c2c4e7fdc700d8345c1c5752644cb`. Use the global `cli.json` on v2, not v1's `tui.json`. +The [README](../README.md#opencode-v2-experimental) shows the release Git install pinned to `v0.19.2`. The earlier Git experiment below used commit `d8050f765b6c2c4e7fdc700d8345c1c5752644cb`. Use the global `cli.json` on v2, not v1's `tui.json`. To test local changes instead, create a fresh artifact directory and build a tarball with `npm pack --ignore-scripts --pack-destination /absolute/path/to/artifacts`. Configure that artifact in `cli.json`: @@ -31,7 +31,7 @@ To test local changes instead, create a fresh artifact directory and build a tar { "plugins": [ { - "package": "vimcode@file:/absolute/path/to/artifacts/vimcode-0.19.1.tgz", + "package": "vimcode@file:/absolute/path/to/artifacts/vimcode-0.19.2.tgz", "options": { "updateCheck": false, "experimentalV2Leader": "ctrl+x" } } ] diff --git a/package.json b/package.json index 157313d..a71c355 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "vimcode", - "version": "0.19.1", + "version": "0.19.2", "description": "Vim keybindings for the OpenCode prompt", "author": "Ori Bar-ilan", "license": "MIT", diff --git a/src/version.ts b/src/version.ts index 6da052e..7775cee 100644 --- a/src/version.ts +++ b/src/version.ts @@ -1,5 +1,5 @@ // Keep in sync with package.json on each release. -export const VERSION = "0.19.1"; +export const VERSION = "0.19.2"; // GitHub API returns fresh content immediately; raw.githubusercontent.com // is CDN-cached for up to 5 minutes which delays update detection. From b2009fa03df39eb31aebb9fe63c7f42486c3a277 Mon Sep 17 00:00:00 2001 From: ori Date: Wed, 14 Oct 2026 00:24:14 +0300 Subject: [PATCH 2/2] docs: date v0.19.2 release Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 8c10684..ec6db6d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -8,7 +8,7 @@ Format follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/). Version ## [Unreleased] -## [0.19.2] — 2026-10-13 +## [0.19.2] — 2026-10-14 ### Added