Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .github/workflows/record-backend-prod-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ jobs:
- name: Checkout code
uses: actions/checkout@v4
with:
ref: main
fetch-depth: 0

- name: Setup Node
Expand Down
33 changes: 31 additions & 2 deletions ops/backend-release-dispatch.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,36 @@ Backend production deploy success must call the frontend repository with `reposi
```json
{
"event_type": "backend-prod-deployed",
"client_payload": {}
"client_payload": {
"release_id": "prod-20260517-2100",
"env": "prod",
"summary": "backend patch release",
"backend": {
"repo": "study-platform-mvp",
"image": "zeroone-backend:v1.4.3-b7c8d9e",
"commit": "b7c8d9e",
"version": "v1.4.3",
"changed": true
},
"database": {
"changed": true,
"migration_version": "V45",
"migration_files": [
"src/main/resources/db/migration/V45__create_course_refund.sql"
]
},
"rollback": {
"backend": "zeroone-backend:v1.4.2-a1b2c3d"
},
"metadata": {
"release_intent": "patch",
"bootstrap_mode": false,
"previous_deploy_image": "zeroone-backend:v1.4.2-a1b2c3d",
"pull_request_number": 1234,
"pull_request_labels": ["release:patch", "db:backup-confirmed"],
"backend_deploy_id": "backend-prod-123"
}
}
}
```

Expand All @@ -21,7 +50,7 @@ The frontend workflow that receives this event is:
.github/workflows/record-backend-prod-release.yml
```

## Required payload
## Required `client_payload`

```json
{
Expand Down
2 changes: 1 addition & 1 deletion ops/rollback.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,4 +24,4 @@ Rollback is based on fixed image tags recorded in `releases/`, never on pointer
3. Deploy the fixed frontend/backend images.
4. Run backend health check.
5. Run frontend smoke/E2E check.
6. Record the rollback outcome in a follow-up release/incident note.
6. Record the rollback outcome in a new `releases/prod-*.yaml` release record, then link any follow-up incident note from that record or the incident tracker.
Loading