versioning · compatibility
Version the whole contract together.
Schema, field catalogue, semantic engine, index snapshots, examples and tools form one release unit.
Compatibility policy
| Change | Version | Provider action |
|---|---|---|
| Documentation clarification; no validation change | patch | none |
| Optional field or non-breaking rule addition | minor | review; adopt when useful |
| Required field, meaning, removal or stricter rejection | major | migrate and revalidate |
| Controlled-index snapshot refresh | release metadata | review diff before pinning |
v1.0.0-rc.3 · 2026-08-22
- Locked validation while an example fixture is loading.
- Verified the seven-property summary only after the full source reaches the editor.
v1.0.0-rc.2 · 2026-08-22
- Mapped all 27 current property create controls to public XML or explicit internal importer policy.
- Added every fixed value set, all 34 content locales and direct access to every controlled choice.
- Expanded examples to seven visible properties covering all property types, statuses and transaction modes.
- Added focused sale, rental and new-build feeds to downloads, CLI generation and the browser workbench.
- Added contract and multi-browser coverage for the new create and example surfaces.
v1.0.0-rc.1 · 2026-08-22
- Initial strict XSD 1.0 contract mapped to the propertyfeedtemplate model.
- Complete production-controlled catalogue snapshot with JSON/CSV artifacts and manifest.
- Minimal, maximum-data and three deliberately invalid fixtures.
- Browser workbench and searchable index explorer.
- Authoritative CLI validation, media audit, index export/diff and sample generation.
- Media rules, language integration examples and rollback-safe platform inclusion plan.
Kyero v3.9 compatibility baseline
v1 retains complete-snapshot feeds, stable listing identity, modified timestamps, lowercase elements, UTF-8, multilingual text, ordered images, floorplan roles and explicit sale/rental semantics. It deliberately replaces free-text matching with real controlled IDs, adds separate listing/display/internal identity contracts, stronger media metadata, explicit lifecycle status and hierarchical semantic validation.