Specification versions, compatibility and migration

Current record

This page records only the version verifiable in the current repository. Other historical releases, dates and freeze decisions have not been confirmed, so no older versions or migration history are invented. MotionGit initiates and maintains the specification; named maintainers and the freeze process remain to be confirmed.

Current specification · 中文 · English

Compatibility rules

specVersion must equal 0.1.0-draft.1. The Schema and static inspector support the same range. Unknown versions must fail; do not execute their templates. The specification version and a template’s own template.version have different meanings. For an unknown runtime profile, show instructions, preview and download without claiming runtime support.

Inspector behavior correction

The earlier inspector accepted the 0.1 prefix, potentially accepting unimplemented versions. This update requires the exact current version; it does not publish a new specification version. Packages previously accepted by the permissive check but declaring other versions now fail. Maintainers must inspect their actual fields and runtime contracts rather than merely relabeling the version to pass checks.

Migration entry

No migration between confirmed specification releases can currently be listed. Preserve the original package and recheck locally, retaining the actual version and authoring declaration. Stop for an unsupported version; determine the real contract and compatibility before adapting it.

Each future actual release must document its release date, field and semantic changes, breaking effects, supported Schema and inspector range, executable migration steps and conformance samples. Keep Draft until a freeze decision is confirmed.