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: applications/polkadot-runtime-releaser.md
+11-18Lines changed: 11 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,10 +23,6 @@ Especially to the new teams, they might not have enough experience to handle it.
23
23
- The rustc/OS version affects the compiled artifacts.
24
24
- There are also some unclear things of the srtool.
25
25
- E.G. https://substrate.stackexchange.com/questions/11686/getting-error-rust-nightly-not-installed-when-starting-an-srtool-container-to-bua
26
-
- When to notify the community to upgrade the node?
27
-
- Collator/Validator nodes should be upgraded first.
28
-
- RPC suppliers should be upgraded later.
29
-
- I saw some EVM RPCs require the runtime version to be equal to the node version.
30
26
- How to host a wasm-override repository for the community?
31
27
- Debug log WASM.
32
28
- We always use `sp-api/disable-logging` in the release build, so no more detail logs in the general runtime.
@@ -45,30 +41,26 @@ For any Polkadot-SDK-based chain, they could use PRR to release their runtime. I
45
41
For PRR's utilization, the chain team requires two repositories: one for their code and another for the release.
46
42
47
43
Take `foo-network` as an example.
48
-
They should have two repositories, `foo-network/foo` and `foo-network/foo-release`.
44
+
They should have two repositories, `foo-network/foo` and `foo-network/foo-runtime-overrides`.
49
45
50
46
`foo-network/foo` is the base Polkadot-SDK-based chain repository that everyone should have.
51
47
52
-
`foo-network/foo-release` is a new repository that PRR requires.
48
+
`foo-network/foo-runtime-overrides` is a new repository that PRR requires.
53
49
It will have 2 branches, `foo` and `bar` if they have 2 networks, `foo`(mainnet) and `bar`(canary network).
54
50
It will host the override WASMs and the release under the corresponding network branch.
55
51
56
-
For collator/validator nodes, they should monitor the `foo-network/foo` repository release as usual.
57
-
For RPC suppliers or service node, they should monitor the `foo-network/foo-release` repository release, it's a more stable version. It will only be published once the on-chain runtime upgrade get confirmed.
58
-
59
52
PRR will supply these components, which will all be hosted in one repository.
60
53
- A GitHub Action to response the try-runtime. (Users can comment something like `/bot try-runtime <network>` under a release PR to trigger this action.)
61
54
- A GitHub Action to build the release runtime.
62
55
- A GitHub Action to notify release repository there is a new release that release repository can start preparing the override WASMs.
63
-
- A GitHub Action and a tool to monitor the on-chain runtime version and compare it with the release runtime version to trigger the release on the release repository.
64
56
- A tool to build and manage the override WASMs.
57
+
- A tool to inspect the basic information from the WASM file.
| try-runtime | Comment `/bot try-runtime <network>` under the PR. | Bot will comment the try-runtime result under the PR. |
69
-
| Runtime release | Usually by tag, this can be configured by users. | Build and release the runtime files. |
70
-
| WASM override | Runtime release action will notify this action. | Build and push the runtime files to the repository. |
71
-
| Node release | It's a scheduled action that runs every hour by default. | Retrieve the on-chain runtime version and compare it with the latest GitHub tag to determine if a release is necessary. |
0 commit comments