You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/releasing/README.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ Remember to use the appropriate versioning for your release.
23
23
1. Create your branch, usually from the tip of the `master` branch:
24
24
25
25
```bash
26
-
git fetch origin master:master
26
+
git fetch origin master
27
27
git checkout master
28
28
git checkout -b "releases/$VERSION_RC"
29
29
```
@@ -93,7 +93,7 @@ Remember to use the appropriate versioning for your release.
93
93
11. Create and push a tag from the `master` branch:
94
94
95
95
```bash
96
-
git fetch origin master:master
96
+
git fetch origin master
97
97
git checkout master
98
98
# Double check the tip of the master branch is the expected commit
99
99
# of the squashed release branch
@@ -388,7 +388,7 @@ export P_VERSION=v0.7.4
388
388
```
389
389
1. Create a branch, from the tip of the `master` branch after the release PR has been merged:
390
390
```bash
391
-
git fetch origin master:master
391
+
git fetch origin master
392
392
git checkout master
393
393
git checkout -b "prep-$P_VERSION-release"
394
394
```
@@ -414,6 +414,13 @@ export P_VERSION=v0.7.4
414
414
```
415
415
416
416
This message can help you figure out what the correct RPC chain VM protocol version (here `39`) has to be in compatibility.json for your current release. Alternatively, you can refer to the [Avalanchego repository `version/compatibility.json` file](https://github.com/ava-labs/avalanchego/blob/main/version/compatibility.json) to find the RPC chain VM protocol version matching the AvalancheGo version we use here.
417
+
1. Commit your changes and push the branch
418
+
419
+
```bash
420
+
git add .
421
+
git commit -S -m "chore: prep release $P_VERSION"
422
+
git push -u origin "prep-$P_VERSION-release"
423
+
```
417
424
1. Create a pull request (PR) from your branch targeting master, for example using [`gh`](https://cli.github.com/):
0 commit comments