Skip to content

Commit 015adb2

Browse files
authored
docs: Add upgrade report link in README (#305)
1 parent fc8a48f commit 015adb2

File tree

3 files changed

+20
-11
lines changed

3 files changed

+20
-11
lines changed

.github/workflows/upgrade-facets.yml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
1-
# This is a template workflow for upgrading PoCo facets.
2-
# Update the script path (UPGRADE_SCRIPT environment variable) for each specific upgrade.
1+
# This is a generic workflow that should be used to upgrade PoCo facets.
2+
# Change the environment variable `UPGRADE_SCRIPT` to point to the correct
3+
# script for each specific upgrade.
34

45
name: Upgrade PoCo Facets
56

@@ -16,7 +17,7 @@ on:
1617
default: 'arbitrumSepolia'
1718
dry-run:
1819
description: 'Dry Run (fork test only, no actual deployment)'
19-
required: false
20+
required: true
2021
type: boolean
2122
default: true
2223

docs/README.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -7,6 +7,10 @@
77

88
The detailed API documentation for each Solidity contract — including their functions, events, and data structures — can be found [here](./solidity/index.md).
99

10+
## Upgrades
11+
12+
Reports of all PoCo upgrades are available in [scripts/upgrades/](../scripts/upgrades/)
13+
1014
## Diagrams
1115

1216
### UML diagrams

scripts/upgrades/README.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,26 +1,30 @@
11
# PoCo Smart Contracts Upgrade Guide
22

3-
This document explains the recommended steps for creating and applying a safe, traceable,
4-
and reproducible upgrade to the PoCo Diamond proxy.
3+
This document explains the recommended steps for creating and applying
4+
a safe, traceable, and reproducible upgrade to the PoCo Diamond proxy.
55

66
## Upgrade Steps
77

88
0. **Ensure all tests pass**:<br>
99
Run the full test suite to make sure everything is working before starting an upgrade.
1010

1111
1. **Create a new upgrade script**:<br>
12-
Name the script using the version and upgrade name in the form `vX.Y.Z-upgrade-name.ts`
13-
and implement the upgrade logic.
12+
Name the script using the version and upgrade name format `vX.Y.Z-upgrade-name.ts` and
13+
implement the upgrade logic.
1414

1515
2. **Create a corresponding Markdown report**:<br>
16-
Copy the template file `v0.0.0-template.md` and rename it to match the script's name
17-
(`vX.Y.Z-upgrade-name.md`).
16+
Copy the template file `v0.0.0-template.md` and rename it to match the script file name.
17+
The name should be of the form `vX.Y.Z-upgrade-name.md`.
1818

1919
3. **Test dry-runs locally**:<br>
2020
Use the script [./dry-run.sh](./dry-run.sh) and check the logs.
2121

2222
4. **Update GitHub Actions**:<br>
23-
Modify `upgrade-facets.yml` workflow to call the new upgrade script.
23+
Modify `upgrade-facets.yml` workflow to call the new upgrade script.<br>
24+
Note: to run the upgrade script manually (for testing), use:
25+
```
26+
npx hardhat run scripts/upgrades/vX.Y.Z-upgrade-name.ts --network <network>
27+
```
2428
2529
5. **Upgrade on Testnet**:
2630
- ⚠️ Always upgrade on the testnet first.
@@ -38,4 +42,4 @@ and reproducible upgrade to the PoCo Diamond proxy.
3842
Fill in all required information in `vX.Y.Z-upgrade-name.ts` (tx hashes, logs, ...).
3943
4044
8. **Create a release**
41-
- Use **Release Please** to tag the upgrade version and create the release on GitHub.
45+
- Use **Release Please** to tag the upgraded version and create the release on GitHub.

0 commit comments

Comments
 (0)