Public: anyone can read this; nobody can change it.

release: v0.7.53 — custom tip + releases.json bump (review) #11

Merged opened this view on origin

Check · Review · Land done · Live — Landed; nothing deploys from this branch, so this is the end of its path.

Merged

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.

Notes

shipped merged

opened this view on origin

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

  • 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.
  • Head: review/v0.7.53 @ 7cabd0a (tip 5e9e005 + releases bump).
  • Tree at tip (before bump): 08340a26… — identical to trevato/forge-upstream 442ea5d.
  • Ancestry: main is an ancestor of this branch → merge can be FF-only (prefer that).

Diff summary

Commits ahead of main358 (357 tip + 1 bump)
Behind0
Files (tip vs main)~306 files, +25k / −3.5k
Notablesrc/core/releases.json (new), src/kernel/version.ts (FORGE_VERSION stamp), Dockerfile stamp args, schema.ts migrations 57 → 70, package.json version → 0.0.0 (stamp-driven)

Why 0.7.53 (not retag 0.7.52)

  • Tag v0.7.52 already points at ee580a9 (different tree than tip).
  • Tip still listed only 0.7.52 / migrations 57 while tip has 70 migrations → bump required before an honest tag.
  • This PR adds { "version": "0.7.53", "migrations": 70 } newest-first, keeping the 0.7.52 / 57 row.

After you merge (you press these — not done for you)

# 1) Prefer FF-only merge in the UI, or:
git fetch origin && git checkout main && git merge --ff-only origin/review/v0.7.53
git push origin main

# 2) Tag the merge commit on main (annotated)
git pull --ff-only
git tag -a v0.7.53 -m "v0.7.53"
git push origin v0.7.53
# → release.yml builds image+chart oci://…/trevato-apps/charts/forge:0.7.53

# 3) Pin gitops AFTER chart exists
# edit apps/forge/prod/manifests.yaml:  ref: {tag: "0.7.53"}
# commit+push trevato-apps/gitops (separate PR preferred)

Risks / watchouts

  1. Large jump: live health still reports 0.7.43; gitops already pins chart 0.7.52. This ships migrations 58–70 and a large product surface — expect a real roll.
  2. Additive migrations: after this bump, floor for additive checks uses the two newest counts (70 and 57); migrations 58–70 must remain additive.
  3. Do not force-push / do not retag v0.7.52.
  4. Do not pin gitops until release.yml has published chart 0.7.53.
  5. Prefer FF-only merge; squash would rewrite tip SHAs.

Not in this PR

  • No tag v0.7.53
  • No gitops pin change
  • No merge to main by the preparer
Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs