Public: anyone can read this; nobody can change it.
release: v0.7.53 — custom tip + releases.json bump (review) #11
Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.
Prepared for trevato to review and press the buttons. No tag, no gitops pin, no merge was performed by the preparer. Fast-forward of trevato-apps/forge main (ee580a9 = tag v0.7.52) to the custom tip lineage, plus an honest 0.7.53 entry in src/core/releases.json.
shipped merged
Sign in to join this conversation.
new above
offline
Release review: custom tip →
v0.7.53(draft — do not auto-merge)Prepared for trevato to review and press the buttons. No tag, no gitops pin, no merge was performed by the preparer.
What this PR is
trevato-apps/forgemain(ee580a9= tagv0.7.52) to the custom tip lineage, plus an honest0.7.53entry insrc/core/releases.json.review/v0.7.53@7cabd0a(tip5e9e005+ releases bump).08340a26…— identical totrevato/forge-upstream442ea5d.mainis an ancestor of this branch → merge can be FF-only (prefer that).Diff summary
mainmain)src/core/releases.json(new),src/kernel/version.ts(FORGE_VERSION stamp),Dockerfilestamp args,schema.tsmigrations 57 → 70,package.jsonversion →0.0.0(stamp-driven)Why
0.7.53(not retag0.7.52)v0.7.52already points atee580a9(different tree than tip).0.7.52/ migrations 57 while tip has 70 migrations → bump required before an honest tag.{ "version": "0.7.53", "migrations": 70 }newest-first, keeping the0.7.52/ 57 row.After you merge (you press these — not done for you)
Risks / watchouts
v0.7.52.release.ymlhas published chart0.7.53.Not in this PR
v0.7.53mainby the preparer