Watch a release ride the line

Every Tuesday's train calls at the same five stations. Pick one to see what Milepost does there, or let it run.

The doors close on time

At ten the release branch is cut from main. Anything merged after rides next week, and nobody has to ask.

  • release/214cut from main at 4f1c9e2
  • Aboard38 changes from 4 teams
  • Next cutTue 10:00

Every change shows its ticket

Tests, migrations and the bundle budget run on the branch itself, so a red check names the change that broke it.

  • Unit2,914 passed
  • End to end186 passed
  • Migrations2, both reversible

A dress rehearsal with real data

The train stops on staging for an hour. The teams who own the changes get a link and a checklist, not a meeting.

  • Paymentssigned off
  • Searchsigned off
  • Mobilechecking now

A canary that can stop the train

One in ten requests rides the new release. If errors or latency drift past your limits, it rolls back by itself.

  • Error rate0.21%, limit 0.5%
  • p95 latency184 ms, limit 250 ms
  • Auto-rollbackarmed

Arrived, with the notes written

The release reaches everyone by lunch, and the changelog is drafted from the tickets that rode it.

  • Rollout100%
  • Changelogdrafted, 38 entries
  • Train 215boarding