| commit | 17e80ecea628f5ae47ed330742454bf716a196ab | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Aug 25 17:00:12 2023 +0200 |
| committer | fweikert <fwe@google.com> | Fri Aug 25 17:00:12 2023 +0200 |
| tree | 5bd4c69106e82efd0ace6b2c81a17cbd5c534c6f | |
| parent | 6e3bbe6f5d5e16f2fa55f2afc67cef38c0792e26 [diff] |
Release 7.0.0-pre.20230816.3 (2023-08-25)
Baseline: 27aaccccb674090493d52d3340b7df69f5ed43f8
Cherry picks:
+ baace69c0c7cb2fe927214dae78c43bd10865c43:
Automated rollback of commit
37268de708224bba900036b8b3fe9e123d2eae6d.
Incompatible changes:
- The --android_include_proguard_location_references flag is not
supported anymore.
- The --apple_compiler command line option is not available anymore.
- --no_proguard_location_reference is now added unconditionally to
the command line of aapt2.
- The command line flag --apple_enable_auto_dsym_dbg is not
supported anymore.
Important changes:
- `rule()` and `attr.*` can no longer be (pointlessly) called
during WORKSPACE evaluation and repository rule evaluation.
- Expands baseline profile wildcards before optimizer tools see
them.
This release contains contributions from many people at Google, as well as Chirag Ramani, Fabian Meumertzheim, Keith Smiley, nglevin, Tyler Williams.
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
