pezkuwichain/revive
1
0
Fork 0
mirror of https://github.com/pezkuwichain/revive.git synced 2026-04-22 05:38:00 +00:00
Code Issues Packages Projects Releases Wiki Activity

LLVM release workflows (#207)

Browse Source 
Co-authored-by: xermicus <cyrill@parity.io>
This commit is contained in:
Yuri Volkov
2025-02-20 12:30:52 +01:00
committed by GitHub
parent 89cdfefab4
commit 840a736fc5
2 changed files with 162 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASE.md
+7 -1
View File
@@ -7,4 +7,10 @@ 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
4. Update the [contract-docs](https://github.com/paritytech/contract-docs/) accordingly
# LLVM release
To create a new LLVM release, create a git tag (not GitHub release) with `llvm-` prefix, e.g. `llvm-0.0.11`.
`Release LLVM` action will start automatically. It will create new GitHub release, and upload LLVM binaries.
Other actions including Release will use these binaries on the next run.