mirror of
https://github.com/pezkuwichain/pezkuwi-subxt.git
synced 2026-05-07 01:28:07 +00:00
a70617124b
Closes https://github.com/paritytech/release-engineering/issues/6 Adds a new Github Workflow which on a new release being created, builds and attaches all runtimes managed in this repository in two flavours: - `dev-debug-build`: Built with the `try-runtime` feature and has logging enabled - `on-chain-release`: Built with the regular old `on-chain-release` feature The new Github Workflow could be extended in the future by the @paritytech/release-engineering team to fully automate the release process if they choose to, similar to how it is fully automated in the Fellowship repo (https://github.com/polkadot-fellows/runtimes/blob/main/.github/workflows/release.yml). The `on-chain-release` did not exist for parachains, so I added it. --- Tested on my fork: - https://github.com/liamaharon/polkadot-sdk/actions/runs/6663773523 - https://github.com/liamaharon/polkadot-sdk/releases/tag/test-6 --------- Co-authored-by: Chevdor <chevdor@users.noreply.github.com> Co-authored-by: Dónal Murray <donal.murray@parity.io>
Rococo: v2.1
Rococo is a testnet runtime with no stability guarantees.
How to build rococo runtime
EpochDurationInBlocks parameter is configurable via ROCOCO_EPOCH_DURATION environment variable. To build wasm
runtime blob with customized epoch duration the following command shall be exectuted:
ROCOCO_EPOCH_DURATION=10 ./polkadot/scripts/build-only-wasm.sh rococo-runtime /path/to/output/directory/
How to run rococo-local
The Cumulus Tutorial details building, starting, and
testing rococo-local and parachains connecting to it.
How to register a parachain on the Rococo testnet
The parachain registration process on the public Rococo testnet is also outlined.