@neocompose/cli 0.36.10 → 0.36.12
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
CHANGED
|
@@ -1,5 +1,36 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.36.12] - 2026-08-22
|
|
4
|
+
|
|
5
|
+
### Fixed
|
|
6
|
+
|
|
7
|
+
- Let project owners and admins plan, apply, inspect, and resume history
|
|
8
|
+
rewrites through the CLI device login. The editor profile now requests the
|
|
9
|
+
changelog write grant, the registered OAuth client allows it, and every
|
|
10
|
+
history rewrite endpoint declares its read or write scope. Existing CLI
|
|
11
|
+
sessions must run `neo logout` followed by `neo login` once after upgrading.
|
|
12
|
+
|
|
13
|
+
## [0.36.11] - 2026-08-21
|
|
14
|
+
|
|
15
|
+
### Fixed
|
|
16
|
+
|
|
17
|
+
- Stop `neo status` reconstructing a referenced row twice. Retaining a stored
|
|
18
|
+
NeoScript construction followed reference members and `Reference(...)`
|
|
19
|
+
constructor arguments into rows it merely points at, so lowering order could
|
|
20
|
+
report a false "Source reconstructs value:… with different content" on a
|
|
21
|
+
healthy workspace. The retain sweep now stops at reference boundaries, and
|
|
22
|
+
an authored reconstruction always supersedes a retained copy.
|
|
23
|
+
- Re-lower against the server side of an unresolved conflict. A conflicted
|
|
24
|
+
record whose base body was stale (for example after resolving markers by
|
|
25
|
+
hand without `neo resolve`) made the identity walk miss rows the server
|
|
26
|
+
still holds and re-mint them; the lowering now adopts the server body while
|
|
27
|
+
the push plan keeps comparing against the local base.
|
|
28
|
+
- Refuse to plan value deletions the workspace base cannot explain. When a
|
|
29
|
+
planned delete's row is named by nothing in the base while the same push
|
|
30
|
+
mints replacement rows, `neo status`/`neo push` now report
|
|
31
|
+
`value-base-desync` and plan nothing instead of shipping deletes for live
|
|
32
|
+
server rows; the same shape with no re-mint is reported as a warning.
|
|
33
|
+
|
|
3
34
|
## [0.36.10] - 2026-08-21
|
|
4
35
|
|
|
5
36
|
### Fixed
|