Repository navigation
Releases: camthink-ai/ne30x-app
Releases · camthink-ai/ne30x-app
Release list
v1.0.0
line-crossing v1.0.0
Unsigned NEAPP05 candidate packaged by the repository release pipeline.
Package identity
| Field | Value |
|---|---|
| Repository version | v1.0.0 (release batch identity) |
| App ID | line-crossing |
| Native version | 4.2.8 |
| UI version | 1.2.10 |
| Package format | neapp-v5-unsigned |
| Package size | 478380 bytes |
| Package SHA-256 | 0a3b1ecb5c47d4fbcc1ee464c69a4d7914359461038064e851c2fbb0262b7fc1 |
| Source commit | 8dce6c14933480321b5736306531b547b6bda33f |
| Signing | none: no private key, no SPKI, no signature, no sequence ledger |
Repository version, native version, and UI version are recorded
separately; they are different version lines and may carry equal or
different values.
Changes
Changed
- Merge pull request #1 from harryhua-ai/upstream-import
- initial import: ne30x-app line-crossing app (NEAPP05 unsigned)
- first commit
Compatibility
- Host caps:
0x3ff - Resource quotas: event_max=1576, state_quota=512, control_max=512, snapshot_max=1024, report_max=6144
- Verification boundary:
offline unsigned-format verification only: SHA-256 here checks container/member consistency, never publisher authenticity or anti-rollback; NOT Host admission, install, execution, or device acceptance - Requires device firmware with unsigned NEAPP05 admission enabled.
Verification
- Independent verifier result: PASS
- Verification report: attached as
*.verification.json - Build provenance: attached as
*.provenance.json
Known limitations
- Packages are unsigned NEAPP05 (
neapp-v5-unsigned): no private key, no signature, no sequence ledger. Installation requires device firmware with unsigned-app admission enabled. - Only
line-crossingis packaged today. The pipeline records one app per package; multi-app releases are not produced yet. - The workflow creates unpublished draft releases only. Publishing a draft is a separate, per-version human action after explicit User Release GO.
- The git tag for a draft release is materialized by GitHub from the draft's stored target commit at publish time. After the draft is created, its target commit, notes, and assets must not be edited.
- Batch (repository) version, native version, and UI version are separate version lines recorded in each release note and package provenance.