1 ADR 0041 pre 1 0 versioning and readiness
Forgejo Actions edited this page 2026-09-25 16:38:07 +00:00

ADR 0041: Pre-1.0 Versioning and Readiness Boundary

Status: accepted Date: 2026-05-31

Context

ADR 0019 declared the v1 baseline complete and started release tags at v1.0.0. That was premature. Memories is still pre-live: the only expected installation is Christian's developer instance, and the project is still intentionally changing core data authority boundaries such as the People-to-generic class-instance migration.

Using 1.x versions before public/family readiness creates the wrong expectation. It suggests stable external upgrade compatibility, stable public database/API contracts, and production-grade migration promises. The project should instead reserve 1.0.0 for the first version Christian considers clear and safe enough for real household/public use.

Decision

Memories returns to pre-1.0 semantic versioning.

  1. Current development resumes at 0.41.0.

  2. 1.0.0 is reserved for the first public/family-ready release.

  3. Historical pre-live tags that were incorrectly created as v1.* are renamed to v0.* without changing their target commits:

    Old tag New tag
    v1.0.0 v0.1.0
    v1.1.0 v0.2.0
    v1.1.1 v0.2.1
    v1.2.1 v0.3.1
    v1.3.0 v0.4.0
  4. Pre-1.0 minor versions may include breaking application, API, or database changes when a spec/ADR documents the pre-live migration/reset posture.

  5. Pre-1.0 compatibility promises remain strict for original media bytes and explicit backup/reset instructions, but not for stable external database/API upgrades.

  6. Runtime application metadata, Docker image tags, package metadata, API contract metadata, and export sourceAppVersion should use the aligned pre-1.0 app version.

1.0.0 Readiness Boundary

1.0.0 requires an explicit readiness decision. At minimum, that decision must confirm:

  • no known intentional legacy authority layers remain in core runtime paths;
  • backup/restore and destructive migration posture are clear for non-developer installations;
  • public/family-facing workflows intended for first real use are coherent enough for household use;
  • upgrade expectations from 1.0.0 onward are documented;
  • release tags and app version metadata use the v1.0.0 boundary intentionally, not as an internal progress marker.

Consequences

  • Existing v1.* pre-live tags were removed from the remote and replaced with equivalent v0.* tags.
  • Any local clone that fetched the old v1.* tags must prune or delete them manually.
  • Existing developer exports or logs that mention 1.x versions are historical pre-live artifacts, not public stability evidence.
  • The next runtime/product version is 0.41.0, not 1.41.0.
  • Future agents must not bump to 1.0.0 unless a spec/ADR explicitly performs the readiness decision.

Revisit Triggers

Revisit this ADR if:

  • Memories is shared with external users before the planned 1.0 readiness decision;
  • separate versioning is needed for API contracts, workers, CLI, or web clients;
  • restore-from-export becomes a supported fidelity restore path;
  • release automation needs compatibility matrices across independently versioned components.