From 4dca40d85f569f38c420307b6cf5159d11cb9a40 Mon Sep 17 00:00:00 2001 From: kemurayama <7068107+kemurayama@users.noreply.github.com> Date: Tue, 12 Dec 2023 10:03:37 +0900 Subject: [PATCH] Updated to 1.8.1 (#1677) Changed release semantic versions: 1.8.1 --- .github/ISSUE_TEMPLATE/release.md | 10 +++++----- Makefile | 2 +- cloudbuild.yaml | 2 +- install/helm/open-match/Chart.yaml | 4 ++-- install/helm/open-match/values.yaml | 2 +- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md index 03fadec05..1f21542b5 100644 --- a/.github/ISSUE_TEMPLATE/release.md +++ b/.github/ISSUE_TEMPLATE/release.md @@ -49,7 +49,7 @@ otherwise there should already be a `release-0.5` branch so run, git checkout -b release-0.5 upstream/release-0.5 ``` -**NOTE: The branch name must be in the format, `release-X.Y` otherwise** +**NOTE: The branch name must be in the format, `release-X.Y.Z` otherwise** **some artifacts will not be pushed.** ## Releases & Versions @@ -97,7 +97,7 @@ releases. Find {version} and replace with the current release (e.g. 0.5.0) only required once.** - [ ] Create the branch in the **upstream** repository. It should be named - release-X.Y. Example: release-0.5. At this point there's effectively a code + release-X.Y.Z. Example: release-0.5. At this point there's effectively a code freeze for this version and all work on main will be included in a future version. If you're on the branch that you created in the *getting setup* section above you should be able to push upstream. @@ -106,7 +106,7 @@ only required once.** git push origin release-0.5 ``` -- [ ] Announce a PR freeze on release-X.Y branch on [open-match-discuss@](https://groups.google.com/forum/#!forum/open-match-discuss). +- [ ] Announce a PR freeze on release-X.Y.Z branch on [open-match-discuss@](https://groups.google.com/forum/#!forum/open-match-discuss). - [ ] Open the [`Makefile`](makefile-version) and change BASE_VERSION entry. - [ ] Open the [`install/helm/open-match/Chart.yaml`](om-chart-yaml-version) and change the `appVersion` and `version` entries. - [ ] Open the [`install/helm/open-match/values.yaml`](om-values-yaml-version) and change the `tag` entries. @@ -114,7 +114,7 @@ git push origin release-0.5 - [ ] There might be additional references to the old version but be careful not to change it for places that have it for historical purposes. - [ ] Update usage requirements in the Installation doc - e.g. supported minikube version, kubectl version, golang version, etc. - [ ] Create a PR with the changes, include the release candidate name, and point it to the release branch. -- [ ] Go to [open-match-build](https://pantheon.corp.google.com/cloud-build/triggers?project=open-match-build) and update all *post submit* triggers' `_GCB_LATEST_VERSION` value to the `X.Y` of the release. This value should only increase as it's used to determine the latest stable version. +- [ ] Go to [open-match-build](https://pantheon.corp.google.com/cloud-build/triggers?project=open-match-build) and update all *post submit* triggers' `_GCB_LATEST_VERSION` value to the `X.Y.Z` of the release. This value should only increase as it's used to determine the latest stable version. - [ ] Merge your changes once the PR is approved. Note: the helm chart is not published to the public registry until the merge is complete (it's a second cloud build trigger upon merge), so you won't be able to do final release testing until after all checks/approvals are finished! ## Create a release branch in the upstream open-match-docs repository @@ -132,7 +132,7 @@ only required once.** - [ ] Create a *draft* [release](https://github.com/googleforgames/open-match/releases). Note that github has both "Pre-release" and "draft" as different concepts for a release. Until the release is finalized, only use "Save draft", and do not use "Publish release". - [ ] Use the [release template](https://github.com/googleforgames/open-match/blob/main/docs/governance/templates/release.md) - [ ] `Tag = v{version}` (Example: v0.5.0. Append -rc.# for release candidates. Example: v0.5.0-rc.1.) - - [ ] `Target = release-X.Y` (Example: release-0.5.) + - [ ] `Target = release-X.Y.Z` (Example: release-0.5.) - [ ] `Release Title = v{version}` (Must match `Tag`) - [ ] `Write` section will contain the contents from the [release template](https://github.com/googleforgames/open-match/blob/main/docs/governance/templates/release.md). - [ ] Add the milestone to all PRs and issues that were merged since the last milestone. Look at the [releases page](https://github.com/googleforgames/open-match/releases) and look for the "X commits to main since this release" for the diff. diff --git a/Makefile b/Makefile index 026e406f3..d1d91e431 100644 --- a/Makefile +++ b/Makefile @@ -53,7 +53,7 @@ # If you want information on how to edit this file checkout, # http://makefiletutorial.com/ -BASE_VERSION = 1.8.0 +BASE_VERSION = 1.8.1 SHORT_SHA = $(shell git rev-parse --short=7 HEAD | tr -d [:punct:]) BRANCH_NAME = $(shell git rev-parse --abbrev-ref HEAD | tr -d [:punct:]) VERSION = $(BASE_VERSION)-$(SHORT_SHA) diff --git a/cloudbuild.yaml b/cloudbuild.yaml index b86515c5e..40005fce8 100644 --- a/cloudbuild.yaml +++ b/cloudbuild.yaml @@ -185,7 +185,7 @@ artifacts: - api/*.swagger.json substitutions: - _OM_VERSION: "1.8.0" + _OM_VERSION: "1.8.1" _GCB_POST_SUBMIT: "0" _GCB_LATEST_VERSION: "undefined" _ARTIFACTS_BUCKET: "gs://open-match-build-artifacts/" diff --git a/install/helm/open-match/Chart.yaml b/install/helm/open-match/Chart.yaml index 1a4386ee5..11f8e5ee2 100644 --- a/install/helm/open-match/Chart.yaml +++ b/install/helm/open-match/Chart.yaml @@ -13,8 +13,8 @@ # limitations under the License. apiVersion: v2 -appVersion: "1.8.0" -version: 1.8.0 +appVersion: "1.8.1" +version: 1.8.1 name: open-match dependencies: - name: redis diff --git a/install/helm/open-match/values.yaml b/install/helm/open-match/values.yaml index ff3c201c3..342b8c055 100644 --- a/install/helm/open-match/values.yaml +++ b/install/helm/open-match/values.yaml @@ -278,7 +278,7 @@ global: # Use this field if you need to override the image registry and image tag for all services defined in this chart image: registry: gcr.io/open-match-public-images - tag: 1.8.0 + tag: 1.8.1 pullPolicy: Always # Expose the telemetry configurations to all subcharts because prometheus, for example,