Skip to content

Commit 1e9c3c3

Browse files
chore: prep next release v0.7.10 (#1723)
1 parent 5689967 commit 1e9c3c3

File tree

4 files changed

+13
-5
lines changed

4 files changed

+13
-5
lines changed

RELEASES.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Release Notes
22

3-
## Pending Release
3+
## [v0.7.10](https://github.com/ava-labs/subnet-evm/releases/tag/v0.7.10)
44

55
- Add pending releases here
66

compatibility.json

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,6 @@
11
{
22
"rpcChainVMProtocolVersion": {
3+
"v0.7.10": 43,
34
"v0.7.9": 43,
45
"v0.7.8": 43,
56
"v0.7.7": 42,

docs/releasing/README.md

Lines changed: 10 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Remember to use the appropriate versioning for your release.
2323
1. Create your branch, usually from the tip of the `master` branch:
2424

2525
```bash
26-
git fetch origin master:master
26+
git fetch origin master
2727
git checkout master
2828
git checkout -b "releases/$VERSION_RC"
2929
```
@@ -93,7 +93,7 @@ Remember to use the appropriate versioning for your release.
9393
11. Create and push a tag from the `master` branch:
9494

9595
```bash
96-
git fetch origin master:master
96+
git fetch origin master
9797
git checkout master
9898
# Double check the tip of the master branch is the expected commit
9999
# of the squashed release branch
@@ -388,7 +388,7 @@ export P_VERSION=v0.7.4
388388
```
389389
1. Create a branch, from the tip of the `master` branch after the release PR has been merged:
390390
```bash
391-
git fetch origin master:master
391+
git fetch origin master
392392
git checkout master
393393
git checkout -b "prep-$P_VERSION-release"
394394
```
@@ -414,6 +414,13 @@ export P_VERSION=v0.7.4
414414
```
415415
416416
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+
```
417424
1. Create a pull request (PR) from your branch targeting master, for example using [`gh`](https://cli.github.com/):
418425
```bash
419426
gh pr create --repo github.com/ava-labs/subnet-evm --base master --title "chore: prep next release $P_VERSION"

plugin/evm/version.go

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ var (
99
// GitCommit is set by the build script
1010
GitCommit string
1111
// Version is the version of Subnet EVM
12-
Version string = "v0.7.9"
12+
Version string = "v0.7.10"
1313
)
1414

1515
func init() {

0 commit comments

Comments
 (0)