EOL.WikiEOL.Wiki
← ← Back to all products

Bazel

Active
Tools & MonitoringLatest Version: 9.1.1Latest Release: Jun 3, 2026

Bazel is a fast, scalable build and test tool by Google supporting multiple languages and platforms.

Support summary

Bazel has cycles in security-only maintenance. Production workloads should move toward actively supported releases.

What do EOL and support statuses mean?

Next EOL

Dec 31, 2026

Bazel 7 · 190 days left

Supported cycles

3

6 lts

Versions

6

Latest Version

9.1.1

Active Support

1

EOL

3

Lifecycle Timeline

Today
9
9
8
8
7
7
6
6
5
5
4
4
Active SupportSecurity SupportEOL

Versions

ReleaseRelease DateActive SupportEOLLatest VersionLTSStatus
9Jan 20, 2026YesDec 31, 20289.1.1
Yes
Active
8Dec 9, 2024Jan 20, 2026Dec 31, 20278.7.0
Yes
Security
7Dec 11, 2023Dec 9, 2024Dec 31, 20267.7.1
Yes
Security
6Dec 19, 2022Dec 11, 2023Dec 31, 20256.6.0
Yes
EOL
5Jan 19, 2022Dec 19, 2022Jan 31, 20255.4.1
Yes
EOL
4Jan 21, 2021Jan 19, 2022Jan 31, 20244.2.4
Yes
EOL

Data sources

Frequently Asked Questions

Which versions of Bazel have reached end of life?
The following Bazel versions have reached end of life and no longer receive security updates: 6, 5, 4. It is recommended to upgrade to a supported version.
Is it safe to continue using Bazel 6?
Bazel 6 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Bazel?
The latest version of Bazel is 9.1.1, released in the 9 release cycle.
How many versions of Bazel are currently supported?
Bazel currently has 3 actively supported version(s): 9, 8, 7.
When does Bazel 9 reach end of life?
Bazel 9 is scheduled to reach end of life on Dec 31, 2028.
What should I do when Bazel reaches end of life?
When a Bazel version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.