Repository navigation
chore(build): upgrade Bazel to 9.3.0 - #21
Merged
Merged
Conversation
Select Bazel 9.3.0 for development, CI and release builds. Regenerate the module lockfile with Bazel 9.3.0 while preserving the first-party rule and Go SDK pins.
realityforge
force-pushed
the
codex/upgrade-bazel-9-3-0
branch
from
October 7, 2026 22:44
40a4988 to
b78fa50
Compare
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.
Use Bazel 9.3.0 for local development, CI and release builds. The wrapper and workflows already use the repository's
.bazelversionpin.Regenerate the module lockfile with 9.3.0, which writes format 28 and updates its bundled dependency metadata, including
apple_support2.5.2. The first-partyrules_go0.61.1 and Go 1.26.4 pins are unchanged; no compatibility fixes were needed.Audited tracked Bazel pins, wrappers, workflows, scripts, documentation and workspace files. There are no nested first-party workspaces or additional version pins.
Local verification
All commands below exited 0 on macOS arm64. Both version commands printed
bazel 9.3.0; the full suite passed all 30 test targets, the integration suite passed seven targets (cached from the full run), lint reported0 issues., and the executable printedbraid 0.0.0-dev. The dedicated output directory avoids the shared output directory in the local user configuration. Formatting and subsequent builds produced no further tracked changes;git diff --exit-codealso passed after committing.The pull request CI will verify Linux amd64 quality checks and integration on Windows amd64, Linux arm64, macOS amd64 and macOS arm64 before merge.