Release Mimir v2.13.1

[aknuds1]

• Publish Mimir v2.13.1
  • Write release notes
    • Ensure the any change to release notes in main has been cherry picked to the release branch
  • Update version in release- branch
    • VERSION
    • CHANGELOG
    • operations/mimir/images.libsonnet (_images.mimir and _images.query_tee fields)
    • operations/mimir-rules-action/Dockerfile (grafana/mimirtool image tag)
  • Execute make build-jsonnet-tests and commit to release branch
  • Tag the release

    git checkout release-<version>
    ./tools/release/tag-release.sh

  • Wait until the CI pipeline succeeds
  • Create a release on GitHub

    git checkout release-<version>
    ./tools/release/create-draft-release.sh

  • Merge the release branch release- into main

    ./tools/release/create-pr-to-merge-release-branch-to-main.sh

    This prepares a PR into main branch. On approval, use the merge-approved-pr-branch-to-main.sh script, following the instruction on how to merge the PR with "Merge commit" (i.e. we DO NOT "Squash and merge" this one).
  • If during the release process settings in the renovate.json5 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.json5, renovate.json5 should keep updated the following branches:
    main, release-3.1 and release-3.0.
  • Announce the release on socials
  • Open a PR to add the new version to the backward compatibility integration test (integration/backward_compatibility.go)
    • Keep the last 3 minor releases
  • Open a PR to update the mixin in "Self-hosted Grafana Mimir" integration
    • This is addressed by Grafana Labs
  • Publish dashboards to grafana.com
    • This is addressed by Grafana Labs
  • After publishing a GEM release publish the mimir-distributed Helm chart. Follow the instructions in Release process for a final release