@neocompose/cli 0.43.1 → 0.45.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
CHANGED
|
@@ -1,5 +1,42 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.45.0] - 2026-09-03
|
|
4
|
+
|
|
5
|
+
### Changed
|
|
6
|
+
|
|
7
|
+
- Remove the unused `formatVersion` and `contractVersion` fields from the
|
|
8
|
+
in-memory project schema manifest. Manifest producers, validators, source
|
|
9
|
+
lowering, and NeoScript analysis now share one current structural contract.
|
|
10
|
+
|
|
11
|
+
## [0.44.0] - 2026-09-03
|
|
12
|
+
|
|
13
|
+
### Added
|
|
14
|
+
|
|
15
|
+
- `neo doctor --fix` deletes the rows the document audit's
|
|
16
|
+
`unprojected-value-row` findings name: base value rows no emitted file
|
|
17
|
+
projects and no other record names, which `neo status` reads as CLI-managed
|
|
18
|
+
loose state and never reports. It lists every orphan root with the number of
|
|
19
|
+
rows it owns, confirms, then deletes them under two staleness guards: the CAS
|
|
20
|
+
base the last pull recorded for each row, and the version head each
|
|
21
|
+
transaction expects from the one before it, starting from the head that pull
|
|
22
|
+
left. A project that moved on since the pull therefore fails the commit
|
|
23
|
+
instead of deleting a row that has since gained an owner, and a workspace
|
|
24
|
+
with no recorded head is refused rather than written blind. Sweeps larger
|
|
25
|
+
than one transaction go up in batches sized from the shared cost model.
|
|
26
|
+
`--yes` answers the confirmation for scripted runs; `--fix` has no `--json`
|
|
27
|
+
form.
|
|
28
|
+
|
|
29
|
+
### Fixed
|
|
30
|
+
|
|
31
|
+
- `neo pull` marked a conflicted record in only the one file the emission
|
|
32
|
+
attributes it to, so a conflict on a member declared by more than one class
|
|
33
|
+
(system world-layer members such as `Name`) left the sibling declarations
|
|
34
|
+
unmarked. Resolving the marked file alone then left the declarations
|
|
35
|
+
disagreeing and the next command refused the workspace. Markers now go in
|
|
36
|
+
every file that declares the record, and `neo resolve` treats those files as
|
|
37
|
+
one conflict: it settles them together and refuses a record whose
|
|
38
|
+
declarations are only partly resolved.
|
|
39
|
+
|
|
3
40
|
## [0.43.1] - 2026-09-03
|
|
4
41
|
|
|
5
42
|
### Changed
|