opencode-plugin-flow 3.1.0 → 3.2.0
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/CHANGELOG.md +12 -0
- package/README.md +19 -2
- package/dist/index.js +42 -42
- package/dist/index.js.map +6 -5
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -2,6 +2,18 @@
|
|
|
2
2
|
|
|
3
3
|
## [Unreleased]
|
|
4
4
|
|
|
5
|
+
## [3.2.0] - 2026-06-13
|
|
6
|
+
|
|
7
|
+
Stale installs become visible: a passive update notice, the running version in `/flow-status`, and documented update steps
|
|
8
|
+
|
|
9
|
+
OpenCode caches plugin installs per spec string and never re-resolves them, so a user can keep running an old Flow version with no signal anywhere. Plugin startup now schedules a background check against the npm `latest` dist-tag and logs a one-line notice when a newer release exists, including the exact pin to set. The notice is best-effort and fire-and-forget: a 3-second timeout, fail-silent on any network or registry error, never blocking startup, and never touching the user's `opencode.json` — the pin is the user's intent and is only ever reported, not rewritten. Set `FLOW_DISABLE_UPDATE_CHECK=1` to opt out (the test suite, install smoke, and bundle sanity set it so they stay network-free).
|
|
10
|
+
|
|
11
|
+
`flow_status` now reports the running plugin version in its install check — `details.pluginVersion` plus the passing summary line — so "which version did OpenCode actually load?" has a first-class answer instead of requiring a dig through the cache directory.
|
|
12
|
+
|
|
13
|
+
The README gains an "Updating" section documenting the two-restart exact-pin bump workflow, the cache-clear step required for range pins, and the update-notice opt-out.
|
|
14
|
+
|
|
15
|
+
Not-tested: The live notice against the real npm registry from inside an OpenCode host (the check path is covered by dependency-injected tests; the registry endpoint and payload shape were verified by hand).
|
|
16
|
+
|
|
5
17
|
## [3.1.0] - 2026-06-12
|
|
6
18
|
|
|
7
19
|
Only the v3 surface remains: five commands, seven tools, no v2 leftovers
|
package/README.md
CHANGED
|
@@ -29,11 +29,11 @@ Add Flow to the `plugin` array in your `opencode.json` (global `~/.config/openco
|
|
|
29
29
|
|
|
30
30
|
```json
|
|
31
31
|
{
|
|
32
|
-
"plugin": ["opencode-plugin-flow@3"]
|
|
32
|
+
"plugin": ["opencode-plugin-flow@3.2.0"]
|
|
33
33
|
}
|
|
34
34
|
```
|
|
35
35
|
|
|
36
|
-
OpenCode installs the package from npm on startup. Pin
|
|
36
|
+
OpenCode installs the package from npm on the first startup and caches it per spec string under `~/.cache/opencode/packages/<spec>/` — it does **not** re-resolve the version on later startups. Pin an exact version and bump the pin to upgrade: a changed spec string installs fresh. See [Updating](#updating) below.
|
|
37
37
|
|
|
38
38
|
On startup the plugin syncs its global skills, commands, and review agent into OpenCode's normal discovery paths:
|
|
39
39
|
|
|
@@ -50,6 +50,23 @@ On startup the plugin syncs its global skills, commands, and review agent into O
|
|
|
50
50
|
|
|
51
51
|
Sync is ownership-aware: each Flow-owned skill folder carries a `.flow-skill-version` marker with a sha256 line per shipped file, and each synced command/agent file has a sidecar `.flow-version` marker. Folders or files without Flow markers are never touched, and if you edit a Flow-owned file by hand the previous content is backed up next to it before an update replaces it.
|
|
52
52
|
|
|
53
|
+
### Updating
|
|
54
|
+
|
|
55
|
+
OpenCode never auto-updates plugins: the cached install for a given spec string is reused as-is on every startup. Flow therefore checks npm in the background after startup and logs a one-line notice when a newer release exists — it only notifies and never edits your `opencode.json`. Set `FLOW_DISABLE_UPDATE_CHECK=1` to turn the check off.
|
|
56
|
+
|
|
57
|
+
To update with an exact pin (recommended):
|
|
58
|
+
|
|
59
|
+
1. Change the pin in `opencode.json` to the new version, e.g. `"opencode-plugin-flow@3.2.0"`.
|
|
60
|
+
2. Restart OpenCode once to install the new version, and a second time so the freshly re-synced skills, commands, and agents are discovered.
|
|
61
|
+
|
|
62
|
+
If you pinned a range like `@3` instead, the spec string never changes, so the cache entry must be cleared by hand before restarting:
|
|
63
|
+
|
|
64
|
+
```bash
|
|
65
|
+
rm -rf ~/.cache/opencode/packages/opencode-plugin-flow@3
|
|
66
|
+
```
|
|
67
|
+
|
|
68
|
+
`/flow-status` shows the running plugin version in its install check, so you can always confirm which version OpenCode actually loaded.
|
|
69
|
+
|
|
53
70
|
### Per-project skill overrides
|
|
54
71
|
|
|
55
72
|
Skills are plain markdown and deliberately overridable. To customize Flow's behavior for one project — for example a team-specific planning or review rubric — place a project-local skill at:
|