Pin bazel version to 7.5.0, and require up-to-date lockfile for CI#795
Merged
Conversation
…I build Bazel 7 is currently in maintenance and supported to the end of 2026. The CI build should require an up-to-date lockfile so that we can try to catch before merging if Bazel dep changes are made without the corresponding lockfile change.
Otherwise if the submodule is initialized Bazel will try to build it when running commands like bazel test //...:all. But that doesn't work because the cpp-jsonnet directory is not part of the same bazel module. Perhaps there is a better way to fix it but just ignoring the cpp-jsonnet directory seems to be ok.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bazel 7 is currently in maintenance and supported to the end of 2026.
The CI build should require an up-to-date lockfile so that we can try to catch before merging if Bazel dep changes are made without the corresponding lockfile change.
The Bazel lockfile is specific to the Bazel version (because Bazel itself is considered a build dependency), so the recommendation is to use Bazelisk to build with a specific Bazel version: https://bazel.build/external/lockfile#best-practices