From 4c4993ba85ef3fec27ff84b4f5f8ff3e21bece58 Mon Sep 17 00:00:00 2001 From: Justin Carper Date: Tue, 29 Sep 2026 11:14:20 -0500 Subject: [PATCH] chore(release): 0.10.0-next.1 --- CHANGELOG.md | 18 ++++++++++++------ README.md | 4 ++++ package-lock.json | 4 ++-- package.json | 2 +- 4 files changed, 19 insertions(+), 9 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 7d8e4ff..ab8b359 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,18 @@ All notable changes to this project will be documented in this file. ## [Unreleased] +## [0.10.0-next.1] — 2026-09-29 (pre-release) + +Adds opencode v2 support alongside v1 (#127). Not on `latest`; install with +`npm install @stablekernel/opencode-cursor@next` to test. v1 now requires +opencode 1.18.29+ (object plugin entrypoint). `0.10.0-next.0` was tagged but +never published (its release job failed at the npm publish step), so this is +the first published build with v2 support. + +Behind a registry mirror, a fresh pre-release can fail to install with +`ETARGET` until the mirror syncs the new version; retry later or point npm +at `https://registry.npmjs.org`. + - **Fix: opencode v2 loads the provider package at the plugin's own version.** v2 registered the provider with the bare package name, which opencode resolves to `latest` — so a plugin installed from `@next` (or any other @@ -15,12 +27,6 @@ All notable changes to this project will be documented in this file. `file://` builds keep working. v1 is unaffected (its provider is loaded in-process, not via the package specifier). -## [0.10.0-next.0] — 2026-09-29 (pre-release) - -Adds opencode v2 support alongside v1 (#127). Not on `latest`; install with -`npm install @stablekernel/opencode-cursor@next` to test. v1 now requires -opencode 1.18.29+ (object plugin entrypoint). - - **Add: opencode v2 support (dual v1/v2 plugin entrypoint).** The default export is now a dual object: the v2 `{ id, setup }` shape plus the v1 `server()` entrypoint. opencode v1 (>= 1.18.29) calls `server()` as before; diff --git a/README.md b/README.md index 741dc74..cc7c156 100644 --- a/README.md +++ b/README.md @@ -88,6 +88,10 @@ opencode v2 uses a `plugins` key (plural) and loads the plugin's `setup()` entry Both generations load the same published package, so one install serves either. Minimum versions: v1 >= 1.18.29 (object plugin entrypoint), v2 tested against 2.0.19. +**Registry mirrors:** on v2 the provider package is installed at exactly the plugin's +version, so behind a registry mirror a fresh release can fail with `ETARGET` until the +mirror syncs it. Retry later, or point npm at `https://registry.npmjs.org`. + On v2 the plugin registers the Cursor provider (pinned to the session directory via `settings.cwd`, so the agent runs in your project even when the v2 runner process was started elsewhere), the model catalog with real per-model cost diff --git a/package-lock.json b/package-lock.json index 2a44792..df9b7c0 100644 --- a/package-lock.json +++ b/package-lock.json @@ -1,12 +1,12 @@ { "name": "@stablekernel/opencode-cursor", - "version": "0.10.0-next.0", + "version": "0.10.0-next.1", "lockfileVersion": 3, "requires": true, "packages": { "": { "name": "@stablekernel/opencode-cursor", - "version": "0.10.0-next.0", + "version": "0.10.0-next.1", "license": "MIT", "dependencies": { "@connectrpc/connect-node": "^2.1.2", diff --git a/package.json b/package.json index f011a85..1939ab3 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@stablekernel/opencode-cursor", - "version": "0.10.0-next.0", + "version": "0.10.0-next.1", "description": "opencode provider plugin backed by the official Cursor SDK (@cursor/sdk) — adds a Cursor provider and lists its models", "type": "module", "license": "MIT",