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: RELEASE_CHECKLIST.md
+10-2Lines changed: 10 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -32,7 +32,7 @@ Changes flow one way, `next` → `staging` → `main`, and the promotion pull re
32
32
-**`staging`** receives `next`. A pull request into it requires every entry in the staging section to run the source version, checked with `VERIFY_STAGING_DEPLOYMENTS`.
33
33
-**`main`** receives `staging`. A pull request into it requires every entry in the production section to run the source version, carry no prerelease suffix, and be owned by a Safe, checked with `VERIFY_PRODUCTION_DEPLOYMENTS`.
34
34
35
-
The flags gate the deployment testsin the contracts and the crates suites alike; unset, the gated tests skip and no chain is forked.
35
+
The flags gate the deployment tests, which live in the bindings crate beside the record they check; unset, they skip and no chain is forked.
36
36
37
37
Deploy or upgrade **every** chain of an environment before opening its promotion pull request — one chain left behind blocks the promotion for all of them.
38
38
@@ -176,7 +176,7 @@ For each chain in the `staging` section of the record:
176
176
-[ ] After the last chain, confirm the promotion gate locally by running
177
177
178
178
```sh
179
-
VERIFY_STAGING_DEPLOYMENTS=true just contracts-test bindings-test
179
+
VERIFY_STAGING_DEPLOYMENTS=true just bindings-test
180
180
```
181
181
182
182
the same checks the promotion pull request runs.
@@ -359,6 +359,14 @@ For **both**:
359
359
360
360
The genesis fields pin how the address was derived and cannot be recovered from the chain once the proxy is upgraded. They are written once and never edited.
361
361
362
+
-[ ] Regenerate the library the deploy script reads the record through with
363
+
364
+
```sh
365
+
just contracts-gen-deployments
366
+
```
367
+
368
+
and commit it alongside the record. The contracts package ships without `deployments.json`, so the deploy script reads the records from the generated [`./contracts/generated/RecordedDeployments.sol`](./contracts/generated/RecordedDeployments.sol); leaving it stale lets a genesis deploy run twice on the same chain. CI reruns the generator and fails on any diff.
369
+
362
370
-[ ] Bump the `bindings` package version in [`./crates/bindings/Cargo.toml`](./crates/bindings/Cargo.toml) to `A.B.0`, where `A` is the last `MAJOR` version and `B` is the last `MINOR` version number incremented by 1.
363
371
364
372
-[ ] Run `just bindings-build` and check that the `Cargo.lock` file reflects the version number change, then run the tests with `just bindings-test`.
0 commit comments