@matuto-ai/opencode-broker-connector 0.1.0 → 0.1.1

package/README.md

@@ -46,10 +46,10 @@ Optional `broker.caFile` points to a trusted private CA; public certificates nor
 
 ## After npm publication
 
-The package is prepared as `@matuto-ai/opencode-broker-connector`. **A prepared package/workflow does not mean it has been published.** Once version `0.1.0` exists on npm, use this native OpenCode configuration instead of the local file:
+The package is prepared as `@matuto-ai/opencode-broker-connector`. **A prepared package/workflow does not mean it has been published.** Once version `0.1.1` exists on npm, use this native OpenCode configuration instead of the local file:
 
 ```json
-{"plugin": ["@matuto-ai/opencode-broker-connector@0.1.0"]}
+{"plugin": ["@matuto-ai/opencode-broker-connector@0.1.1"]}
 ```
 
 OpenCode installs npm plugins automatically using Bun. Keep the same private `PSST_CONFIG_FILE`; remove the duplicate local entry so the plugin does not load twice. See [publication](docs/publishing.md).

package/docs/publishing.md

@@ -5,7 +5,7 @@ Package name: `@matuto-ai/opencode-broker-connector`. The npm workflow follows t
 1. Review and merge the feature PR.
 2. Bootstrap the package under an npm account authorized for this package if it does not exist yet. Account creation, credentials and first publication are operator actions, not performed by the connector.
 3. Configure npm's GitHub Actions trusted publisher for owner `matuto-ai`, repository `opencode-broker-connector`, workflow `npm-publish.yml`. If the repository moves, update package metadata and trusted-publisher settings together.
-4. Create a GitHub release whose tag exactly matches `v` + package.json version (first `v0.1.0`).
+4. Create a GitHub release whose tag exactly matches `v` + package.json version (next `v0.1.1`).
 5. The action runs syntax, tests including pinned actual CLI, package inspection, then `npm publish --access public --provenance` using OIDC. No long-lived npm token is stored in the workflow.
 6. Confirm npm has the exact version before recommending npm installation. Failed publishing is not repaired by silently changing a version or recreating a tag.
 
@@ -13,12 +13,13 @@ Package name: `@matuto-ai/opencode-broker-connector`. The npm workflow follows t
 
 Before npm publication, the local-file installation in README works directly from `main` after the naming PR is reviewed and merged. No unpublished dependency is required.
 
-## Scoped package transition
+## Patch release
 
-Publication is paused while the `@matuto-ai` naming changes are reviewed.
-The package version remains `0.1.0`; existing unscoped npm packages and old
-GitHub release tags are not renamed, overwritten, or republished by this change.
-After merge, the maintainer must verify npm organization permissions and configure
-the scoped package trusted publisher. A later release must point at the reviewed
-scoped commit and its tag must exactly match the package version; do not reuse
-an old tag pointing to unscoped code. Version/tag planning is a separate step.
+This PR prepares `0.1.1`; the intended GitHub release tag is `v0.1.1`.
+After review and merge, the maintainer can publish that release from the merged
+commit to exercise npm Trusted Publishing. This code change does not itself
+create a tag, release, or npm publication. Verify the workflow succeeds and the
+scoped npm version exists before recommending it for installation.
+
+Existing `0.1.0` npm packages and old GitHub tags remain untouched. Do not reuse
+or move an old release tag; the new tag must exactly match the package version.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@matuto-ai/opencode-broker-connector",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "type": "module",
   "engines": {
     "node": ">=24.19.0 <25"