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
1. Check `spec_version` value in [runtime's lib.rs](./substrate/bin/node/runtime/src/lib.rs). There are 2: one for mainnet and one for testnet. They should be the same and higher than the last release.
6
+
2. Check `version` in [runtime's Cargo.toml](./substrate/bin/node/runtime/Cargo.toml). Major version should match the `spec_version`.
7
+
3. Check `version` in [cli's Cargo.toml](./substrate/bin/node/cli/Cargo.toml). Major version should match the `spec_version`. This is the version that will be used as the name of the release and tag.
8
+
9
+
## Release
10
+
11
+
1. Go to the [Release new version](https://github.com/liberland/liberland_substrate/actions/workflows/release.yml) action in GitHub, select `Run workflow`, choose the branch (usually `develop` or `main`) and run it. This action will do the following:
12
+
* Run unit-tests
13
+
* Run `try-runtime` migration checks (which detects things like state inconsitencies or pallet/state version mismatches)
14
+
* Run fork test for both bastiat and mainnet and check if whole state is still parsable post-fork
15
+
* Build runtimes in a reproducible way
16
+
* Build new binary
17
+
* Create a new GitHub Release
18
+
* Build & publish new Docker Image
19
+
2. Wait for the `Release new version` action to finish.
20
+
3. Go to [GitHub Releases](https://github.com/liberland/liberland_substrate/releases). New release should be there, ready for deployment.
21
+
4. (Optional) Open a new PR that bumps versions for the next release. [Sample PR](https://github.com/liberland/liberland_substrate/pull/404/files).
0 commit comments