opencode-plugin-flow 7.0.1 → 7.0.2
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 +27 -0
- package/README.md +3 -3
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -6,6 +6,33 @@ One short entry per release, written for users deciding whether to upgrade.
|
|
|
6
6
|
|
|
7
7
|
No changes yet.
|
|
8
8
|
|
|
9
|
+
## [7.0.2] - 2026-07-27
|
|
10
|
+
|
|
11
|
+
Documentation only. The docs still called the product Flow v6 two majors after
|
|
12
|
+
the fact, including the sentence in `CONTEXT.md` whose whole job is to name the
|
|
13
|
+
generation.
|
|
14
|
+
|
|
15
|
+
- Where naming the generation is the point, it now reads v7. Where the version
|
|
16
|
+
added nothing to the sentence it is gone, so the claim cannot go stale a third
|
|
17
|
+
time: the layering diagram, the maintainer contract's invariants, and the
|
|
18
|
+
README's version-change note all describe Flow rather than a numbered Flow.
|
|
19
|
+
- The forward-reading compatibility note said newer builds accept state written
|
|
20
|
+
by earlier *v6* builds, which stopped being the full truth when 7.0.0 shipped.
|
|
21
|
+
It now says earlier builds.
|
|
22
|
+
- References to the v6 cutover itself are unchanged, because that boundary is
|
|
23
|
+
genuinely v6: pre-v6 active state is still not migrated, and the absence of a
|
|
24
|
+
cross-version gate still rests on v6 having been a hard cutover.
|
|
25
|
+
|
|
26
|
+
No source, dependency, or behaviour change. The Session v5 schema and every
|
|
27
|
+
durable document are exactly as in 7.0.1, so there is nothing here to upgrade
|
|
28
|
+
for unless you read the docs from the package.
|
|
29
|
+
|
|
30
|
+
Install or update:
|
|
31
|
+
|
|
32
|
+
```bash
|
|
33
|
+
opencode plugin opencode-plugin-flow@7.0.2 --global --force
|
|
34
|
+
```
|
|
35
|
+
|
|
9
36
|
## [7.0.1] - 2026-07-27
|
|
10
37
|
|
|
11
38
|
Dependency currency, with one bump that changes what is actually tested:
|
package/README.md
CHANGED
|
@@ -20,7 +20,7 @@ context change, or a lost transcript.
|
|
|
20
20
|
Install the exact npm release through OpenCode:
|
|
21
21
|
|
|
22
22
|
```bash
|
|
23
|
-
opencode plugin opencode-plugin-flow@7.0.
|
|
23
|
+
opencode plugin opencode-plugin-flow@7.0.2 --global --force
|
|
24
24
|
```
|
|
25
25
|
|
|
26
26
|
Omit `--global` for project scope. Version pins are exact and never update on
|
|
@@ -31,7 +31,7 @@ The equivalent manual project configuration is:
|
|
|
31
31
|
```json
|
|
32
32
|
{
|
|
33
33
|
"$schema": "https://opencode.ai/config.json",
|
|
34
|
-
"plugin": ["opencode-plugin-flow@7.0.
|
|
34
|
+
"plugin": ["opencode-plugin-flow@7.0.2"]
|
|
35
35
|
}
|
|
36
36
|
```
|
|
37
37
|
|
|
@@ -42,7 +42,7 @@ or activation CLI, and removing the plugin entry disables it. If two Flow copies
|
|
|
42
42
|
load for one project, both fail closed until the duplicate is removed.
|
|
43
43
|
|
|
44
44
|
**Changing versions.** Finish or explicitly close any active session first, in
|
|
45
|
-
either direction. Flow
|
|
45
|
+
either direction. Flow opens only Session v5 active state, and an older build
|
|
46
46
|
cannot be trusted to read state a newer one has already written. Older archives
|
|
47
47
|
remain inert history, and there is no migration or rollback layer.
|
|
48
48
|
|