Skip to content

Commit c4b262f

Browse files
committed
Add more steps
1 parent 92023af commit c4b262f

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

libevm/tooling/release/README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -24,3 +24,26 @@ In the following, we create a release candidate tag `v1.13.14-0.2.0.rc.4`.
2424
1. Commit your modifications to [params/version.libevm.go](/params/version.libevm.go) with a commit title `chore: release v1.13.14-0.2.0.rc.4`.
2525
1. Push your modified branch to the remote `git push`
2626
1. Open a pull request from your modified branch `myusername/release/v1.13.14-0.2.0.rc.4` and targeting `release/v1.13.14-0.2.0.rc.4`, for example with `https://github.com/ava-labs/libevm/compare/release/v1.13.14-0.2.0.rc.4...myusername/release/v1.13.14-0.2.0.rc.4?expand=1`. Set the tile to "chore: release `v1.13.14-0.2.0.rc.4`"
27+
1. Wait for all the checks to pass on the pull request
28+
1. Fast forward merge your branch in the release branch:
29+
30+
```bash
31+
git checkout release/v1.13.14-0.2.0.rc.4
32+
git merge --ff-only myusername/release/v1.13.14-0.2.0.rc.4
33+
git push
34+
```
35+
36+
This will also close the ongoing pull request.
37+
1. Finally create your tag and push it using the release branch:
38+
39+
```bash
40+
git tag v1.13.14-0.2.0.rc.4
41+
git push v1.13.14-0.2.0.rc.4
42+
```
43+
44+
1. (optional) you can then cleanup with:
45+
46+
```bash
47+
git branch -D release/v1.13.14-0.2.0.rc.4 myusername/release/v1.13.14-0.2.0.rc.4
48+
git push -d origin myusername/release/v1.13.14-0.2.0.rc.4
49+
```

0 commit comments

Comments
 (0)