Skip to content

Commit

Permalink
chore: bumping version to 0.19.0 (#854)
Browse files Browse the repository at this point in the history
  • Loading branch information
amirvalhalla authored Dec 11, 2023
1 parent 6964e77 commit 7128878
Show file tree
Hide file tree
Showing 3 changed files with 13 additions and 13 deletions.
10 changes: 5 additions & 5 deletions docs/patching.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,13 +7,13 @@ To patch a released version, start by creating a dedicated branch for that versi
Let's create environment variables for the patch version. For the rest of this document, we will use these environment variables in the commands.

```bash
PRV_VER="0.17.0"
CUR_VER="0.17.0"
NEXT_VER="0.17.1"
PRV_VER="0.18.0"
CUR_VER="0.18.0"
NEXT_VER="0.18.1"
TAG_NAME="v${CUR_VER}"
TAG_MSG="Version ${CUR_VER}"
BASE_BRANCH="0.17.x"
BASE_VER="0.17.0"
BASE_BRANCH="0.18.x"
BASE_VER="0.18.0"
```

For the rest of this document, we will use these environment variables in commands.
Expand Down
12 changes: 6 additions & 6 deletions docs/releasing.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@ Let's create environment variables for the release version.
For the rest of this document, we will use these environment variables in the commands.

```bash
PRV_VER="0.17.0"
CUR_VER="0.18.0"
NEXT_VER="0.19.0"
PRV_VER="0.18.0"
CUR_VER="0.19.0"
NEXT_VER="0.20.0"
TAG_NAME="v${CUR_VER}"
TAG_MSG="Version ${CUR_VER}"
BASE_BRANCH="main"
Expand Down Expand Up @@ -82,7 +82,7 @@ Wait for the PR to be approved and merged into the base branch.

7. **Tagging**

Create a git tag:
Create a Git tag and sign it using your [GPG key](https://docs.github.com/en/authentication/managing-commit-signature-verification/about-commit-signature-verification) with the following commands:

```bash
git checkout ${BASE_BRANCH}
Expand All @@ -109,8 +109,8 @@ Pushing the tag will automatically create a release tag and build the binaries.
9. **Bumping version**

Update the version inside the [version.go](../version/version.go) and add `beta` to the `meta` field.
Update [patching](./patching.md) docuemnt.
If this is a majore release, update the version inside this document in step 3.
Update [patching](./patching.md) document.
If this is a major release, update the version inside this document in step 3.

Create a new PR against base branch:

Expand Down
4 changes: 2 additions & 2 deletions version/version.go
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ import (
// These constants follow the semantic versioning 2.0.0 spec (http://semver.org/)
const (
major uint = 0
minor uint = 18
minor uint = 19
patch uint = 0
meta string = ""
meta string = "beta"
protocolVersion uint = 1
)

Expand Down

0 comments on commit 7128878

Please sign in to comment.