mirror of
https://github.com/AikidoSec/safe-chain.git
synced 2026-05-26 04:00:49 +00:00
Add doc about release process
This commit is contained in:
parent
f1307c6d82
commit
b116bc7016
1 changed files with 25 additions and 0 deletions
25
docs/Release.md
Normal file
25
docs/Release.md
Normal file
|
|
@ -0,0 +1,25 @@
|
|||
# Release Guide
|
||||
|
||||
## Steps
|
||||
|
||||
### 1. Create and push a version tag
|
||||
|
||||
```bash
|
||||
git tag 1.0.0
|
||||
git push origin 1.0.0
|
||||
```
|
||||
|
||||
This triggers the build pipeline, which compiles binaries for all platforms and creates a draft GitHub release.
|
||||
|
||||
### 2. Wait for artifacts to build
|
||||
|
||||
Monitor the [Actions tab](https://github.com/AikidoSec/safe-chain/actions) until the `Create Release` workflow completes.
|
||||
|
||||
### 3. Publish the GitHub release
|
||||
|
||||
1. Go to the [Releases page](https://github.com/AikidoSec/safe-chain/releases)
|
||||
2. Open the draft release created for your tag
|
||||
3. Add release notes
|
||||
4. Click **Publish release**
|
||||
|
||||
Publishing the release automatically triggers an npm publish. Pre-release versions (e.g. `1.0.0-beta`) are published to npm under a tag matching the pre-release identifier (e.g. `beta`). Stable versions are published to the `latest` tag.
|
||||
Loading…
Add table
Add a link
Reference in a new issue