Upgrading notes — toward v1.12

Copy Markdown View Source

This page tracks maintainer-facing and adopter-facing expectations for the planning milestone v1.12 (trust, evidence, and adoption polish). SemVer for the library on Hex follows mix.exs and CHANGELOG.md; planning milestones are coordination labels in .planning/ — not a second installable version axis on Hex (see CHANGELOG.mdPlanning milestones vs Hex releases).

v1.12 tightens the trust bundle across phases 73–75: a bounded SEED-002 audit batch (planning truth in 09-03), a single UAT outcome index for the eight GA·UAT SEED rows, and alignment with the machine vs human coverage catalog in docs/uat-ci-coverage.md. The eight-row SEED outcome table exists only in .planning/v1.12-UAT-EVIDENCE.md — do not copy or paraphrase that matrix here.

For v1.11 adoption stabilization context, see Upgrading notes — toward v1.11.

After v1.11 (planning milestone)

If you have not read v1.11 upgrade notes yet, read Upgrading notes — toward v1.11 first — v1.12 builds on that baseline.

Library / host upgrade checklist

  1. Bump {:sigra, ...} in the host mix.exs using CHANGELOG.md and Hex release notes as the source of truth.
  2. Run mix deps.get, then mix compile and mix test (or your CI equivalent).
  3. Skim CHANGELOG.md and Maintaining Sigra for breaking or host-app steps for your line; use MAINTAINING for maintainer release ritual pointers around evidence URLs when cutting minors/majors.

Unless CHANGELOG.md documents a breaking change for your line, no new mix sigra.upgrade steps are implied by the v1.12 planning milestone alone.

See also