From a49eb7d4f579706061e021f71a387981de064d5e Mon Sep 17 00:00:00 2001 From: hagen1778 Date: Tue, 29 Oct 2024 18:50:40 +0100 Subject: [PATCH] docs: add step for updating VM version in docs See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7388 Signed-off-by: hagen1778 --- docs/Release-Guide.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/Release-Guide.md b/docs/Release-Guide.md index 7d3a2bb26..9ad1c469b 100644 --- a/docs/Release-Guide.md +++ b/docs/Release-Guide.md @@ -95,6 +95,7 @@ Bumping the limits may significantly improve build speed. 1. Publish release by pressing "Publish release" green button in GitHub's UI. 1. Update GitHub tickets related to the new release. Usually, such tickets have label [waiting for release](https://github.com/VictoriaMetrics/VictoriaMetrics/issues?q=is%3Aopen+is%3Aissue+label%3A%22waiting+for+release%22). Close such tickets by mentioning which release they were included into, and remove the label. See example [here](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/6637#issuecomment-2390729511). 1. Bump VictoriaMetrics version at `deployment/docker/docker-compose.yml` and at `deployment/docker/docker-compose-cluster.yml`. +1. Bump VictoriaMetrics version mentioned in [docs](https://github.com/VictoriaMetrics/VictoriaMetrics/issues/7388). 1. Follow the instructions in [release follow-up](https://github.com/VictoriaMetrics/VictoriaMetrics-enterprise/blob/master/Release-Guide.md). ### Public Announcement