Skip to content

Commit

Permalink
v1.7.1 patch version bump
Browse files Browse the repository at this point in the history
  • Loading branch information
metachris committed Feb 28, 2024
1 parent 03a8c83 commit c2a5d00
Show file tree
Hide file tree
Showing 2 changed files with 10 additions and 7 deletions.
15 changes: 9 additions & 6 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,10 +44,11 @@ curl localhost:18550/eth/v1/builder/status
For example, creating a new release `v1.9`:

1. Create a Github issue about the upcoming release ([example](https://github.com/flashbots/mev-boost/issues/524))
1. Create a release branch (`release/v1.9`)
1. Create an alpha release: `v1.9-alpha1`
1. Test in testnets, iterate as needed, create more alpha versions
1. When tests are complete, create the final release
2. Create a release branch: `release/v1.9` (note: use the target version as branch name, don't add the `-alpha` suffix)
3. Tag an alpha version: `v1.9-alpha1`
4. Test in testnets, iterate as needed, create more alpha versions if needed
5. When tests are complete, create the final tag and release
6.

```bash
# create a new branch
Expand Down Expand Up @@ -83,16 +84,18 @@ docker pull flashbots/mev-boost:v1.9a1

To create a new version (with tag), follow all these steps! They are necessary to have the correct build version inside, and work with `go install`.

* In the release branch
* Update [`Version`](/config/vars.go) to final version to `v1.9`, and commit
* Create final tags, both semver and pep440:
* `git tag -s v1.9`
* `git tag -s v1.9.0`
* Update the `stable` branch:
* `git checkout stable`
* `git merge tags/v1.9 --ff-only`
* `git merge tags/v1.9 --ff-only` (ff-only is important, otherwise git doesn't know the stable branch is based off the v1.9 tag!)
* Update the `develop` branch:
* `git checkout develop`
* `git merge tags/v1.9 --ff-only`
* Update `Version` in `config/vars.go` to next patch with `dev` suffix (eg. `v1.10-dev`) and commit to develop
* Update `Version` in `config/vars.go` to next patch with `dev` suffix (eg. `v1.10-dev`) and commit to `develop` branch
* Now push the `develop` and `stable` branches, as well as the tag: `git push origin develop stable --tags`

Now check the Github CI actions for release activity: https://github.com/flashbots/mev-boost/actions
Expand Down
2 changes: 1 addition & 1 deletion config/vars.go
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ import (

var (
// Version is set at build time (must be a var, not a const!)
Version = "v1.8-dev"
Version = "v1.7.1"

// RFC3339Milli is a time format string based on time.RFC3339 but with millisecond precision
RFC3339Milli = "2006-01-02T15:04:05.999Z07:00"
Expand Down

0 comments on commit c2a5d00

Please sign in to comment.