Require git 2.38 or later for the release gate

0015066efe46 · Devin AI · · parent 5852d4d22a47

Require git 2.38 or later for the release gate

Co-Authored-By: Christopher David <chris@openagents.com>
Co-Authored-By
Christopher David <chris@openagents.com>

Deploy story

What this commit did to the running system — joined from the forge receipt chain, the part a commit page elsewhere cannot show.

Not deployed through the forge lane

No push, promotion, build, or deploy receipt references this commit (receipts are scanned over a bounded recent window). Changes shipped by full node replacement carry their proof in the release gate receipt instead.

Changed files

  • modified docs/operations/production-deploy-runbook.md

Diff

1 file changed, +5 -3

docs/operations/production-deploy-runbook.md modified +5 -3

@@ -30,9 +30,11 @@ Two invariants govern everything:

30 30
The gate fails fast when any of these is missing. Set them up once per
31 31
machine:
32 32
33
1. Tools on `PATH`: `jq`, `mix`, `npm`, `docker`, and `terraform` satisfying
34
   `>= 1.11, < 2.0` (the staging infrastructure gate checks
35
   `ops/staging/infra/versions.tf`).
33
1. Tools on `PATH`: `jq`, `mix`, `npm`, `docker`, `git` version 2.38 or
34
   later (the stack merge and git-plane tests run
35
   `git merge-tree --write-tree`, which older git does not support), and
36
   `terraform` satisfying `>= 1.11, < 2.0` (the staging infrastructure gate
37
   checks `ops/staging/infra/versions.tf`).
36 38
2. JavaScript dependencies: run `npm ci --prefix assets`. The relup stage runs
37 39
   `mix assets.deploy`, which needs `assets/node_modules` (for example
38 40
   `posthog-js`). A missing install fails the relup stage, not the javascript

This page updates live while a promote is in flight · changelog