@neocompose/cli 0.10.6 → 0.11.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 +24 -0
- package/dist/neo.mjs +474 -404
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,29 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [0.11.0] - 2026-07-27
|
|
4
|
+
|
|
5
|
+
### Added
|
|
6
|
+
|
|
7
|
+
- Accept `sortingGroup` as a world system class kind. P40 adds
|
|
8
|
+
`NeoSortingGroup` as a nested class member on `NeoObject`, so every project
|
|
9
|
+
on the migrated schema now carries a class whose `@system` metadata names a
|
|
10
|
+
kind this CLI's manifest validator did not know. Without the release, a
|
|
11
|
+
`neo pull` of any project after the P40 rollout fails validation on the new
|
|
12
|
+
class rather than writing source for it.
|
|
13
|
+
|
|
14
|
+
## [0.10.7] - 2026-07-26
|
|
15
|
+
|
|
16
|
+
### Fixed
|
|
17
|
+
|
|
18
|
+
- Accept an enum option `@id` under the reserved `system_` prefix. Every
|
|
19
|
+
Neo-authored record moved into that namespace (P39 section 1.1c), so a
|
|
20
|
+
`neo pull` of any project on the migrated schema produced source its own
|
|
21
|
+
analyzer then rejected -- sixteen `invalid-enum-option-id` errors across the
|
|
22
|
+
smart tile enums, and no way to complete the pull. The analyzer already
|
|
23
|
+
accepted the prefix; `0.10.6` shipped before that change, so the published
|
|
24
|
+
binary was the only place the old rule survived. No source change, only the
|
|
25
|
+
release that carries it.
|
|
26
|
+
|
|
3
27
|
## [0.10.6] - 2026-07-26
|
|
4
28
|
|
|
5
29
|
### Changed
|