You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/BAD_RELEASE_REPONSE_RUNBOOK.md
+10-11Lines changed: 10 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ The guiding rule is: immutable release history is not rewritten. Recovery happen
18
18
Use this operational runbook before and after public launch. Do not defer recovery practices until after public release. Before treating the release process as ready, ensure:
19
19
20
20
-`template-contract.yml` records `accepted_action` with action tag and SHA.
21
-
-`minimum_compatible_template_version`and `protected_template_refs` are accurate.
-`make template-compat-e2e` gates action releases against current and minimum compatible templates.
23
23
-`make template-release-gates` gates template publication against the accepted action release.
24
24
- Template release notes state compatibility resets explicitly.
@@ -54,7 +54,7 @@ First identify the failure layer:
54
54
4. Template acceptance PR merged but template release/publication failed.
55
55
5. Generated template release exists but publication state is incomplete.
56
56
6. Generated template was published with wrong contents/provenance.
57
-
7. Released action breaks an older protected template.
57
+
7. Released action breaks an older supported template.
58
58
8. Released template gives new users broken setup.
59
59
60
60
Record:
@@ -164,7 +164,7 @@ Corrective release example:
164
164
Corrects the generated template provenance for vA.B.C. Users who copied the previous generated template during the affected window should update from vA.B.D or verify `.reponomics/template-provenance.json`.
165
165
```
166
166
167
-
## 7. Released Action Breaks An Older Protected Template
167
+
## 7. Released Action Breaks An Older Supported Template
168
168
169
169
Impact: compatibility promise violated.
170
170
@@ -216,13 +216,12 @@ Use only when supporting older templates is intentionally no longer viable.
216
216
Required steps:
217
217
218
218
1. Open a PR changing `minimum_compatible_template_version`.
219
-
2. Update `protected_template_refs`.
220
-
3. Explain why older templates are no longer supported.
221
-
4. Add migration guidance.
222
-
5. Add release notes under `## Template release notes`.
223
-
6. Run `make template-compat-e2e`.
224
-
7. Run `make template-release-gates`.
225
-
8. Use a SemVer bump appropriate to user impact. While the project is pre-public and remains on `v0`, a breaking reset does not require a major version bump.
219
+
2. Explain why older templates are no longer supported.
220
+
3. Add migration guidance.
221
+
4. Add release notes under `## Template release notes`.
222
+
5. Run `make template-compat-e2e`.
223
+
6. Run `make template-release-gates`.
224
+
7. Use a SemVer bump appropriate to user impact. While the project is pre-public and remains on `v0`, a breaking reset does not require a major version bump.
226
225
227
226
Example:
228
227
@@ -276,7 +275,7 @@ Use one or more scenarios:
276
275
2. Template acceptance PR merged, but `template-release.yml` failed.
277
276
3. Source template tag exists, but `template-release.yml` failed before generated publication.
278
277
4. Generated template publication completed with wrong provenance.
279
-
5. Action patch release breaks the minimum compatible protected template.
278
+
5. Action patch release breaks the minimum compatible template.
280
279
6. Template release gives new copied repositories broken setup.
0 commit comments