From 63dfd046e54639ac71ac13adf10e16d3612b22ab Mon Sep 17 00:00:00 2001 From: xermicus Date: Wed, 26 Feb 2025 09:38:00 +0100 Subject: [PATCH] Update RELEASE.md (#239) --- RELEASE.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/RELEASE.md b/RELEASE.md index adf0363..9e93bc0 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -4,10 +4,11 @@ Prior to the first stable release we neither have formal release processes nor d To create a new pre-release: -1. Merge a release PR which updates the `-dev.X` versions in the workspace `Cargo.toml` and updates the `CHANGELOG.md` accordingly. The release workflow will attempt to build and publish a new release whenever the latest git tag does not match the cargo package version. -2. Wait for the `Release` workflow to finish. If the workflow fails after the `build-linux-all` step, check if a tag has been created and delete it before restarting or pushing updates. Note: It's more convenient to debug the release workflow in a fork (the fork has to be under the `paritytech` org to access `parity-large` runners). -3. Check draft release on [Releases page](https://github.com/paritytech/revive/releases) and publish (should contain `resolc.js`, `resolc.wasm`, `resolc-web.js`, and `resolc-static-linux` release assets) -4. Update the [contract-docs](https://github.com/paritytech/contract-docs/) accordingly +1. Create a release PR which updates the `-dev.X` versions in the workspace `Cargo.toml` and updates the `CHANGELOG.md` accordingly. Add the `release-test` label to trigger the release workflows. +2. If the CI passes, merge the release PR. The release workflow will attempt to build and publish a new release whenever the latest git tag does not match the cargo package version. +3. Wait for the `Release` workflow to finish. If the workflow fails after the `build-linux-all` step, check if a tag has been created and delete it before restarting or pushing updates. Note: It's more convenient to debug the release workflow in a fork (the fork has to be under the `paritytech` org to access `parity-large` runners). +4. Check draft release on [Releases page](https://github.com/paritytech/revive/releases) and publish (should contain `resolc.js`, `resolc.wasm`, `resolc-web.js`, and `resolc-static-linux` release assets) +5. Update the [contract-docs](https://github.com/paritytech/contract-docs/) accordingly # LLVM release