BazelCon ‘23 is fast approaching! We look forward to connecting with the Bazel community at this year’s hybrid event in which we’ll showcase interesting talks, share the Bazel State-of-the-Union, provide opportunities to collaborate with peers, and have a live Q&A with the Bazel team.
A few updates:
- The preliminary schedule is now available. We'll update this page with speaker information and other details soon. Thank you to everyone who submitted proposals!
- In-person registrations have reached maximum capacity and a waiting list has been opened. Please consider this before booking your trip.
- All main stage talks will be streamed live.
- This year’s Bazel Community Day is co-organized by EngFlow and Tweag, and hosted by Salesforce with happy hour sponsored by Gradle. It is scheduled for Oct 23, a day before BazelCon. Registration is open.
If you have any questions, please reach out to email@example.com.
Bazel 6.4.0 is in progress and scheduled to be released in early October. The first release candidate is already out and ready for testing.
We’re continuing to work towards Bazel 7.0 with the first release candidate tentatively scheduled for Oct 17 and the final release tentatively scheduled for Nov 17. Please keep these dates in mind as you plan and prioritize contributions. Follow the release tracker issue for updates.
Bzlmod: a call for migration
Since the official launch of Bzlmod in Bazel 6.0 in Dec ‘22, the team has been hard at work improving Bzlmod in time for enabling it by default in Bazel 7.0. Read this blog post for details on what's changed since 6.0, what's coming up in 7.0, and a roadmap for the next few years.
We'd like to encourage you to use Bzlmod by default in new projects, and start migration for existing projects. Please respond to this poll to help us understand which rule sets and libraries are most important to unblock your migration.
Since Bazel 6.2.0, we’ve made the following improvements to the lockfile feature:
- A new attribute
environis added to
module_extensionto allow depending on environment variables.
- The module extension will now be re-evaluated in response to changes in the files it depends on.
- Lockfile version bumps will prompt users to refresh it in
- New attributes
arch_dependentare added to
module_extensionto signify its reliance on the operating system or system architecture. When either or both of these attributes are true, separate module extensions will be stored in the lockfile for each distinct combination of operating system and architecture.
Build without the Bytes enabled by default in Bazel 7
We recently turned on Build without the Bytes by default, and the first release to include this change will be Bazel 7.0. Read this blog post for more details.
Removing unused flags
We have started the process of removing and cleaning up unused flags. Refer to this GitHub discussion for more details and reach out if you have any questions or concerns.
- GitHub repository: https://github.com/bazelbuild/bazel
- Releases: https://github.com/bazelbuild/bazel/releases
- Slack chat: https://slack.bazel.build
- Google group: firstname.lastname@example.org
- Special Interest Groups (SIG):
Reach out the email(s) listed below if you’d like to be added to the SIG calendar invites.
|SIG||Meeting frequency||Point of contact|
|Rules authors||Every two email@example.com|
|Android app development||Monthlyfirstname.lastname@example.org|
|Bazel plugin for IntelliJ||Monthlyemail@example.com|
|Remote execution API working group||Monthlyfirstname.lastname@example.org|
Interested in learning about SIGs or starting a new one? Find more information on our website.
Want to get your SIG listed? Please add it to the Community repository.
Ideas, feedback, and submissions are welcome!
Thank you for reading this edition! Let us know if you’d like to see any new information or changes in future community updates by reaching out to email@example.com. We look forward to hearing from you.
Google Bazel team