[x] If a new minor or major version is being released, adjust the settings in the renovate.json configuration on the main branch by adding the new version.
This way we ensure that dependency updates maintain the new version, as well as the latest two minor versions.
For instance, if versions 3.0 and 2.10 are configured in renovate.json, and version 3.1 is being released,
during the release process renovate.json should keep updated the following branches: main, release-3.1, release-3.0 and release-2.10. https://github.com/grafana/mimir/pull/8478
Keep in mind this is a release candidate, so the version string in VERSION and CHANGELOG must end in -rc.#, where # is the release candidate number, starting at 0.
Keep in mind this is a release candidate, so the version string in VERSION and CHANGELOG must end in -rc.#, where # is the release candidate number, starting at 0.
Keep in mind this is a release candidate, so the version string in VERSION and CHANGELOG must end in -rc.#, where # is the release candidate number, starting at 0.
[x] If during the release process settings in the renovate.json have been modified in such a way that dependency updates maintain more than the latest two minor versions,
modify it again to ensure that only the latest two minor versions get updated.
For instance, if versions 3.1, 3.0 and 2.10 are configured in renovate.json, renovate.json should keep updated the following branches:
main, release-3.1 and release-3.0. https://github.com/grafana/mimir/pull/8642
[x] Announce the release on socials
[x] Open a PR to add the new version to the backward compatibility integration test (integration/backward_compatibility_test.go) https://github.com/grafana/mimir/pull/8659
Publish the release candidate (rc.0)
CHANGELOG.md
https://github.com/grafana/mimir/pull/8459./tools/release/check-changelog.sh LAST-RELEASE-TAG...main
and add missing PRs to CHANGELOG## main / unreleased
is blank and at the top. The new section should say## x.y.0-rc.0
../tools/release/notify-changelog-cut.sh
make mixin-screenshots
renovate.json
configuration on themain
branch by adding the new version. This way we ensure that dependency updates maintain the new version, as well as the latest two minor versions. For instance, if versions 3.0 and 2.10 are configured inrenovate.json
, and version 3.1 is being released, during the release processrenovate.json
should keep updated the following branches:main
,release-3.1
,release-3.0
andrelease-2.10
. https://github.com/grafana/mimir/pull/8478-rc.#
, where#
is the release candidate number, starting at 0.mimir-distributed
Helm chart release candidate. Follow the instructions in Release process for a release candidatePublish the release candidate (rc.1)
-rc.#
, where#
is the release candidate number, starting at 0.Publish the release candidate (rc.2)
-rc.#
, where#
is the release candidate number, starting at 0.Publish the stable release
main
has been cherry picked to the release branchoperations/mimir/images.libsonnet
(_images.mimir
and_images.query_tee
fields)operations/mimir-rules-action/Dockerfile
(grafana/mimirtool
image tag)renovate.json
have been modified in such a way that dependency updates maintain more than the latest two minor versions, modify it again to ensure that only the latest two minor versions get updated. For instance, if versions 3.1, 3.0 and 2.10 are configured inrenovate.json
,renovate.json
should keep updated the following branches:main
,release-3.1
andrelease-3.0
. https://github.com/grafana/mimir/pull/8642integration/backward_compatibility_test.go
) https://github.com/grafana/mimir/pull/8659