chore: upgrade to bazel 9 #829

New issue

Closed

opened 2026-03-28 04:28:58 +00:00 by mfreeman451 · 1 comment

mfreeman451 commented

2026-03-28 04:28:58 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2446
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2446
Original created: 2026-01-23T05:39:06Z

No description provided.

Imported from GitHub. Original GitHub issue: #2446 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2446 Original created: 2026-01-23T05:39:06Z --- _No description provided._

mfreeman451 added this to the 1.1.1 milestone

2026-03-28 04:28:58 +00:00

mfreeman451 commented

2026-03-28 04:28:59 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2446#issuecomment-3978736037
Original created: 2026-03-01T00:48:10Z

Started Bazel 9 migration on branch with the following baseline updates:

pinned Bazel to 9.0.0 in .bazelversion
updated Bzlmod deps to Bazel 9-compatible versions (swiftlint, rules_foreign_cc, aspect_bazel_lib, plus direct-dep alignment from resolver warnings)
disabled repo contents cache in .bazelrc (--repo_contents_cache=) to avoid Bazel 9 repo-cache-in-workspace hard error
added explicit load() statements for removed native rules (sh_test, cc_library)

Validation so far:

bazel query //... passes under Bazel 9
bazel build //:gazelle passes under Bazel 9

Next steps: run broader build/test targets in CI profile and fix any rule-level/runtime regressions discovered there.

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2446#issuecomment-3978736037 Original created: 2026-03-01T00:48:10Z --- Started Bazel 9 migration on branch with the following baseline updates: - pinned Bazel to `9.0.0` in `.bazelversion` - updated Bzlmod deps to Bazel 9-compatible versions (`swiftlint`, `rules_foreign_cc`, `aspect_bazel_lib`, plus direct-dep alignment from resolver warnings) - disabled repo contents cache in `.bazelrc` (`--repo_contents_cache=`) to avoid Bazel 9 repo-cache-in-workspace hard error - added explicit `load()` statements for removed native rules (`sh_test`, `cc_library`) Validation so far: - `bazel query //...` passes under Bazel 9 - `bazel build //:gazelle` passes under Bazel 9 Next steps: run broader build/test targets in CI profile and fix any rule-level/runtime regressions discovered there.

mfreeman451 closed this issue

2026-03-28 04:28:59 +00:00