Appearance
26.0.1 — Production change log
Change records
| CR | Class | Target | Env | Reversible | Depends on | Blast radius | Evidence |
|---|---|---|---|---|---|---|---|
| CR-26.0.1-01 | app_build | branch reconciliation | prod | no | — | repository only | #cr-01 |
More records are added as scope is agreed at G0. The five migrations and the Edge Functions already pending promotion to Prod become Change Records at that point — they are not declared yet because they are not yet in an approved scope.
CR-26.0.1-01 — Branch reconciliation
main and uat both sit at 8e8514a (2026-07-10), 48 commits behind develop, and the working branch is 66 ahead of develop. There are zero git tags. deploy-prod.yml refuses a real deploy unless the ref is main, so the pipeline cannot run until this is done — which is why it is CR-01 rather than a housekeeping task.
Sequence: feat/mobile-nativewind-b2 → develop → uat → main, then tag v26.0.1 at the cut.
Irreversible, with a forward fix rather than a rollback: shared branches only move forward. A bad merge is corrected by a follow-up merge, never by rewriting history that others may have pulled.
Build ledger
| Build | Platform | Number | Commit | Submitted | Outcome | Functional delta |
|---|---|---|---|---|---|---|
| none yet |
apps/mobile/app.json is stamped at 26.0.1 / 26000100 for both platforms. If either store rejects, the resubmission takes a new build number on that platform only, and the numbers diverge permanently — see production state for why that is expected rather than a defect.
Contracting changes
| CR | Removes | requires_min_app_build | Oldest live build | Safe? |
|---|---|---|---|---|
| none |
Nothing has ever shipped, so there is no compatibility floor yet and no contracting change is possible in this release by definition.