RayPals/Claro
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

package: reject duplicate project manifest versions

Browse Source
This commit is contained in:
Hermes Agent
2026-09-04 21:07:52 +00:00
parent 20a181b631
commit 5136437e44
6 changed files with 16 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+3 -1
View File
@@ -301,7 +301,9 @@ It also compares the complete `checksum:` field, so extra or trailing checksum
text, or a duplicate checksum field, is rejected as `BAD package checksum`.
Package manifests must contain exactly one `version: 1` field; duplicate or
prefix-matching values such as `version: 10` are rejected as `BAD package version`.
The project manifest must also contain exactly one non-empty `name:` field;
The project manifest must contain exactly one `manifest-version: 1` field; duplicate
or prefix-matching values such as `manifest-version: 10` are rejected as
`BAD project manifest version: expected 1`. It must also contain exactly one non-empty `name:` field;
otherwise doctor reports `BAD project manifest name: expected a non-empty name`.
Starter projects created with `claro new MyProject` use the same `manifest-version: 1` and `lock-version: 1` headers as `claro package init`, so the first project files match the package maintenance tools.