From 69a663dc3b72f10a1251c4d3e438bb0aae5032cb Mon Sep 17 00:00:00 2001
From: John Bartholomew <jpa.bartholomew@gmail.com>
Date: Wed, 21 Jan 2026 14:29:57 +0000
Subject: [PATCH 1/2] ci: check bazel build on the example with multiple bazel
 versions

---
 .github/workflows/build_and_test.yml | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/.github/workflows/build_and_test.yml b/.github/workflows/build_and_test.yml
index e4e3e5f67..561b7f7d8 100644
--- a/.github/workflows/build_and_test.yml
+++ b/.github/workflows/build_and_test.yml
@@ -93,9 +93,15 @@ jobs:
   bazel_use_module:
     name: Build Bazel example
     runs-on: "ubuntu-22.04"
+    strategy:
+      fail-fast: false
+      matrix:
+        bazel_version: ["7.*", "8.*", "9.*"]
     steps:
       - uses: actions/checkout@v4
       - name: Build
+        env:
+          USE_BAZEL_VERSION: ${{ matrix.bazel_version }}
         run: |
           cd examples/bazel
           bazelisk build --lockfile_mode=off //...

From e8ede95ab035827f33c3d80dc79e9723957726bf Mon Sep 17 00:00:00 2001
From: John Bartholomew <jpa.bartholomew@gmail.com>
Date: Wed, 21 Jan 2026 14:43:32 +0000
Subject: [PATCH 2/2] chore: update release checklist to mention checking new
 Bazel releases

---
 release_checklist.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/release_checklist.md b/release_checklist.md
index 83d6229ea..57cc4358e 100644
--- a/release_checklist.md
+++ b/release_checklist.md
@@ -7,6 +7,9 @@ Before doing the release, make sure that the project is in good state:
 - Triage issues – make sure that all issues are labelled.
 - Check for release-blocking bugs. All bugs which results in a wrong result of the evaluation are release-blocking.
 - Go through the open PRs – consider merging any outstanding ones. Do not merge big changes right before the release.
+- Check for new major Bazel versions (https://bazel.build/release), update
+  `.github/workflows/build_and_test.yml` "Build Bazel example" job to check all actively maintained Bazel versions
+  and confirm that it stays green.
 - Sync google/go-jsonnet and google/jsonnet
   1. Check out master from both
   1. Use the `update_cpp_jsonnet.sh` script in the go-jsonnet repository to sync it to jsonnet master.