Last production release
v0.1.0
admin-app · 27 Oct, 07:20 am
Releases · 30 days
4
Production approval
1
Blocked until the release manager signs off
Failed deployments
0
Release management
Staging → approval → production, with rollback prepared before deploy
| Environment | Component | Version | Commit | Deployed | By | Status |
|---|---|---|---|---|---|---|
| production | admin-app | v0.1.0 | a41f9c2 | 27 Oct, 07:20 am | Thokchom Ibohal Singh | succeeded |
| production | api | v1.8.4 | 7de0b13 | 26 Oct, 09:02 pm | Thokchom Ibohal Singh | succeeded |
| staging | business-app | v1.9.0-rc.2 | c92a4fe | 27 Oct, 09:55 am | Moirangthem Chanu Devi | running |
| production | database | migration-0042 | f13b771 | 25 Oct, 11:40 pm | Kshetrimayum Bimol Singh | succeeded |
| production | business-app | v1.8.3 | 9ab771e | 24 Oct, 07:15 pm | Thokchom Ibohal Singh | rolled back |
Release gates
Checked in order; any failure stops the release
| Gate | Checked by | Failure behaviour |
|---|---|---|
| Staging deployment | DevOps Agent | Stop, open incident, notify release manager |
| Smoke and integration tests | QA Agent | Stop, attach failing suite to the task |
| Migration validation | Database Agent | Stop, require a dry-run plan |
| Production approval | Release manager (human) | Hold — no agent may self-approve |
| Post-deploy health | Reliability Agent | Recommend rollback within the watch window |
Rollback policy
Prepared before deployment starts
- Previous artifact and migration down-path recorded before every release.
- Destructive migrations require a documented restore point.
- Rollback is an authorized action, logged with the approving operator.
- Deployments are versioned and reproducible; no hot edits on a server.