Repository navigation
chore(bazel): keep the declared version at 8.8.2 or newer - #193
Merged
Merged
Conversation
lurtz
approved these changes
Nov 2, 2026
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
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.
Policy
minimum-bazel-versionRequire Bazel
8.8.2or newer to address the eMudhra CA security issueacross repositories.
Why this repository?
This repository matches this policy because
.bazelversionexists.Changes
.bazelversion: upgrade from '8.6.0' to '8.8.2'MODULE.bazel.lock: Regenerate MODULE.bazel.lock withbazel mod deps.Tool revision
Generated from eclipse-score/tools at commit
a1e69fa.This pull request is managed by SCORE Repository Policy Sync and may be updated by a later policy run.
Please report any issues to #score-infrastructure.
Note
This pull request is generated automatically. Review the proposed changes
before merging.