opencode-reviewer 0.4.0 → 0.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -3
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -14,7 +14,7 @@ Minimal configuration:
|
|
|
14
14
|
{
|
|
15
15
|
"$schema": "https://opencode.ai/tui.json",
|
|
16
16
|
"plugin": [
|
|
17
|
-
["opencode-reviewer@0.4.
|
|
17
|
+
["opencode-reviewer@0.4.1", {
|
|
18
18
|
"baseURL": "https://api.example.com/v1",
|
|
19
19
|
"model": "your-model",
|
|
20
20
|
"apiKeyEnv": "OPENCODE_REVIEWER_API_KEY"
|
|
@@ -32,7 +32,7 @@ The following expanded example shows **every configuration option**, with all fi
|
|
|
32
32
|
"$schema": "https://opencode.ai/tui.json",
|
|
33
33
|
"plugin": [
|
|
34
34
|
[
|
|
35
|
-
"opencode-reviewer@0.4.
|
|
35
|
+
"opencode-reviewer@0.4.1",
|
|
36
36
|
{
|
|
37
37
|
"baseURL": "https://api.example.com/v1",
|
|
38
38
|
"model": "your-model",
|
|
@@ -63,7 +63,7 @@ This example explicitly enables all five review categories; the three new catego
|
|
|
63
63
|
|
|
64
64
|
### Updates and migration to npm
|
|
65
65
|
|
|
66
|
-
To update, replace `opencode-reviewer@0.4.
|
|
66
|
+
To update, replace `opencode-reviewer@0.4.1` with the desired published version and restart OpenCode. Exact versions keep upgrades intentional; see [npm versions](https://www.npmjs.com/package/opencode-reviewer?activeTab=versions) and [release notes](https://github.com/mightykatun/opencode-reviewer/releases).
|
|
67
67
|
|
|
68
68
|
If you previously registered an extracted bundle, a `file://` URL, or a manually installed `dist/tui.js`, replace that plugin entry with the npm package specifier and preserve its options. Do not keep both entries. Usage history and saved conversation modes remain under OpenCode's state directory, independent of how the plugin is installed. Published npm packages begin with v0.4.0; older releases were distributed as GitHub assets.
|
|
69
69
|
|
|
@@ -214,3 +214,11 @@ npm run check:package # Reproducible build and exact package contents
|
|
|
214
214
|
```
|
|
215
215
|
|
|
216
216
|
Use `OPENCODE_BIN` to select a test binary. Build output is `dist/tui.js`; `npm pack` creates `opencode-reviewer-VERSION.tgz`. See [AGENTS.md](https://github.com/mightykatun/opencode-reviewer/blob/main/AGENTS.md) for maintainer and release details.
|
|
217
|
+
|
|
218
|
+
### Releasing
|
|
219
|
+
|
|
220
|
+
Update both manifests with `npm version X.Y.Z --no-git-tag-version`, commit the release changes, then create and push the matching `vX.Y.Z` tag. A `v*` tag push runs verification and packaging, automatically creates a GitHub Release with generated notes and the archive, and publishes that same archive to npm. No separate GitHub Release creation step is required.
|
|
221
|
+
|
|
222
|
+
Stable versions publish to npm's `latest` tag. Versions such as `X.Y.Z-beta.1` create GitHub prereleases and publish to npm's `next` tag. Package and lockfile versions must match the Git tag; published npm versions are immutable.
|
|
223
|
+
|
|
224
|
+
For an existing tag containing this workflow, use **Actions → Release package → Run workflow**, select `main`, and supply the tag. Equivalent CLI command: `gh workflow run release.yml --ref main -f tag=vX.Y.Z`. Reruns reuse an existing release, and skip npm publication only when the existing package has identical archive integrity.
|