Skip to content

CI: Check bazel build on the example with multiple bazel versions #1266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johnbartholomew merged 2 commits into from
Jan 21, 2026
+9 −0
Merged

CI: Check bazel build on the example with multiple bazel versions #1266

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
69a663d
ci: check bazel build on the example with multiple bazel versions
johnbartholomew Jan 21, 2026
e8ede95
chore: update release checklist to mention checking new Bazel releases
johnbartholomew Jan 21, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .github/workflows/build_and_test.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 //...
3 changes: 3 additions & 0 deletions release_checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
Loading