Full Breakdown
Bazel 9.0 Release: Key Changes and Community Contributions
1/21/2026, 2:48:02 AM
Major Updates in Bazel 9.0
The release of Bazel 9.0 marks a significant milestone in the evolution of the Bazel build system, culminating years of development aimed at enhancing its ecosystem. A primary focus of this release is the complete removal of the legacy WORKSPACE system, which has been replaced by Bzlmod, a package manager that has gained traction in the community since its introduction in 2021. This transition allows for improved dependency management and the introduction of new features, such as a local repository contents cache and an experimental remote repository contents cache.
In addition to the removal of the WORKSPACE system, Bazel 9.0 finalizes the "Starlarkification" effort, which aimed to migrate built-in language rulesets into separate modules written in Starlark. This change enhances the maintainability and flexibility of Bazel, allowing users to update language-specific rules independently from the core Bazel release.
Incompatibilities and Migration Support
As with any major release, Bazel 9.0 introduces several incompatible changes. Users are encouraged to consult the Bazel 9 migration GitHub discussion for assistance during the upgrade process. Notably, Bazel 6 has been deprecated, and no further backports for security or OS compatibility issues will be provided for this version. A final minor release, 6.6.0, was published to address specific incompatibilities with macOS Tahoe.
Community Contributions and Future Developments
The Bazel community has played a crucial role in the development of this release. Notable contributions include the establishment of a new documentation site powered by Mintlify, which is currently in preview mode. Additionally, a new web UI for the Bazel Central Registry has been developed, enhancing search capabilities and module filtering by language and maintainers.
Looking ahead, Bazel 10.0 is set to introduce a typing system for Starlark, responding to community feedback regarding the complexity of Starlark code. This initiative aims to further support ruleset developers in managing their codebases.
Official Statements & Responses
The Bazel team expressed gratitude towards the community for their contributions, stating, "Every little bit helped to make Bazel 9 possible." They encourage ongoing participation through various channels, including GitHub Discussions and the Bazel Slack channel.
Criticism & Opposition
Despite the advancements, some users have voiced concerns regarding the migration process from the WORKSPACE system to Bzlmod, highlighting the challenges associated with transitioning to the new package manager. The Bazel team acknowledges these difficulties and has developed tools to assist users in this migration.
Verbatim Quotes
- “0, we've completely removed the code supporting WORKSPACE.” — Bazel Team
- “We hope you'll continue to participate and follow along through the usual channels: GitHub Discussions, the Bazel Slack channel, @bazelbuild on X (Twitter), the Bazel blog, and the bazel-discuss mailing list.” — Bazel Team
- “Whether it was filing issues, contributing code, or discussing ideas, every little bit helped to make Bazel 9 possible.” — Bazel Team
The release of Bazel 9.0 represents a pivotal shift in the build system's architecture, driven by community engagement and a commitment to modernizing the development experience.
