Tags: bazelbuild/bazel
Tags
[9.0.2] Make include verification aware of Windows case-insensitivity (… …#29214) <!-- Thank you for contributing to Bazel! Please read the contribution guidelines: https://bazel.build/contribute.html --> ### Description <!-- Please provide a brief summary of the changes in this PR. --> ### Motivation <!-- Why is this change important? Does it fix a specific bug or add a new feature? If this PR fixes an existing issue, please link it here (e.g. "Fixes #1234"). --> ### Build API Changes <!-- Does this PR affect the Build API? (e.g. Starlark API, providers, command-line flags, native rules) If yes, please answer the following: 1. Has this been discussed in a design doc or issue? (Please link it) 2. Is the change backward compatible? 3. If it's a breaking change, what is the migration plan? --> No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes <!-- If this is a new feature, please add 'RELNOTES[NEW]: <description>' here. If this is a breaking change, please add 'RELNOTES[INC]: <reason>' here. If this change should be mentioned in release notes, please add 'RELNOTES: <reason>' here. --> RELNOTES: None Commit 79fb843 and 246ea98 --------- Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
Release 10.0.0-pre.20260322.2 (2026-04-01) Baseline: f007411 New features: - Added `--experimental_remote_cache_chunking` flag to read and write large blobs to/from the remote cache in chunks. Requires server support. Important changes: - BEP events will now be written respecting parent-child ordering constraints. - Bzlmod now enforces that integrity strings for patches and overlay files in `source.json` are non-empty. - A `.bazelrc` file may now only `import` files recursively with a depth of up to 512 imports. If you see a "Maximum import depth exceeded parsing config file" error message, check that your workspace genuinely needs to be configured with `.bazelrc` files loading other rc files in a chain as long as 512 files. If you are configured in this way and cannot easily change your `.bazelrc` files to use shorter `import` chains, you may set the `BAZEL_UNLIMITED_IMPORT_DEPTH` environment variable to any value to disable this limit. This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Jake Newfield, John Cater, Justin Won, Tyler French.
Release 10.0.0-pre.20260312.1 (2026-03-19) Baseline: f3ab794 Incompatible changes: - string.splitlines() no longer incorrectly treats u+0085 (NEL) as a newline character Important changes: - Bazel no longer verifies the digests of disk cache entries upon a cache hit. This honors the description but not the previous behavior of the `--remote_verify_downloads` flag, which in fact controlled digest verification for both remote and disk caches. - Bazel now has experimental support for --rewind_lost_inputs, which can rerun actions within a single build to recover from (remote or disk) cache evictions. This release contains contributions from many people at Google, as well as Fabian Meumertzheim, H5-O5, Keith Smiley.
Release 10.0.0-pre.20260308.2 (2026-03-16) Baseline: d67b13a Cherry picks: + eb3941d: Automated rollback of commit 4f793a8. + 51907c4: Release 10.0.0-pre.20260308.2 (2026-03-13) + fc4340c: Release 10.0.0-pre.20260308.2 (2026-03-13) + 7a13594: Release 10.0.0-pre.20260308.2 (2026-03-13) + a933bce: Release 10.0.0-pre.20260308.2 (2026-03-13) + 9b133bc: Release 10.0.0-pre.20260308.2 (2026-03-13) + 9bc159f: Release 10.0.0-pre.20260308.2 (2026-03-13) + e0f3146: Release 10.0.0-pre.20260308.2 (2026-03-14) + 9ef180e: Release 10.0.0-pre.20260308.2 (2026-03-16) + 704831d: Release 10.0.0-pre.20260308.2 (2026-03-16) + 2aebc4d: Release 10.0.0-pre.20260308.2 (2026-03-16) + 8a81d0b: Release 10.0.0-pre.20260308.2 (2026-03-16) Incompatible changes: - `--incompatible_check_testonly_for_output_files` has been flipped. See #28875 for more details. Important changes: - Fix --lockfile_mode=error validation when rolling back changes to module extension facts - `package_group` now supports labels with external repositories in the `packages` attribute. This release contains contributions from many people at Google, as well as Alan Mond, Armando Montanez, Benjamin Peterson, dependabot[bot], Fabian Meumertzheim, Jesse Schalken, John Cater, Keith Smiley, Markus Hofbauer, Michael Mitchell, Ted Kaplan.
Release 10.0.0-pre.20260223.3 (2026-03-06) Baseline: 6dd6396 Cherry picks: + fd860b0: Add alias map cache for command line flag aliases. Incompatible changes: - The environment variable `LC_CTYPE` now defaults to `C.UTF-8` for actions that set `use_default_shell_env = True`, which results in a Unicode-aware locale on essentially all non-EOL Linux distributions, with MSYS2 as well as macOS 15.4 and higher. Pass `--action_env==LC_CTYPE` (note the two `=`s) to explicitly unset this variable, which restores the previous behavior. On older versions of macOS, you can set `--action_env=LC_CTYPE=UTF-8` instead. Important changes: - The `requires-worker-protocol` execution requirement is now forwarded to remote execution services as a platform property (`persistentWorkerProtocol`) to support intermixing JSON and Proto remote persistent worker protocols across a build. - `rctx.symlink` now implicitly watches the target if it falls back to a copy. This release contains contributions from many people at Google, as well as Armando Montanez, Benjamin Peterson, Fabian Meumertzheim, giria660, Joseph Gette, Stefan Penner, Taeyang Jin (Theo), Tyler Breisacher, Tyler French.
[9.0.1] Patch rules_graalvm for Bazel 9 (#28908) Closes #28014. PiperOrigin-RevId: 845680411 Change-Id: I4454ed2731b24ec051ee633460e8bb120fb07d04 <!-- Thank you for contributing to Bazel! Please read the contribution guidelines: https://bazel.build/contribute.html --> ### Description <!-- Please provide a brief summary of the changes in this PR. --> ### Motivation <!-- Why is this change important? Does it fix a specific bug or add a new feature? If this PR fixes an existing issue, please link it here (e.g. "Fixes #1234"). --> ### Build API Changes <!-- Does this PR affect the Build API? (e.g. Starlark API, providers, command-line flags, native rules) If yes, please answer the following: 1. Has this been discussed in a design doc or issue? (Please link it) 2. Is the change backward compatible? 3. If it's a breaking change, what is the migration plan? --> No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes <!-- If this is a new feature, please add 'RELNOTES[NEW]: <description>' here. If this is a breaking change, please add 'RELNOTES[INC]: <reason>' here. If this change should be mentioned in release notes, please add 'RELNOTES: <reason>' here. --> RELNOTES: None Commit: f0ec350 Co-authored-by: Yun Peng <pcloudy@google.com>
[8.6.0] Only use workspace facts for validation with --lockfile_mode=… …error (h… (#28766) …ttps://github.com//pull/28718) When validating the facts in a lockfile with `--lockfile_mode=error`, only use the user-visible lockfile, not the hidden output root lockfile Fixes #28717 No - [X] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). RELNOTES: Fix --lockfile_mode=error validation when rolling back changes to module extension facts Closes #28718. PiperOrigin-RevId: 874282163 Change-Id: I1479dcd6b756dc9d8b01183c4bfe15dd8700aeba <!-- Thank you for contributing to Bazel! Please read the contribution guidelines: https://bazel.build/contribute.html --> ### Description <!-- Please provide a brief summary of the changes in this PR. --> ### Motivation <!-- Why is this change important? Does it fix a specific bug or add a new feature? If this PR fixes an existing issue, please link it here (e.g. "Fixes #1234"). --> ### Build API Changes <!-- Does this PR affect the Build API? (e.g. Starlark API, providers, command-line flags, native rules) If yes, please answer the following: 1. Has this been discussed in a design doc or issue? (Please link it) 2. Is the change backward compatible? 3. If it's a breaking change, what is the migration plan? --> No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes <!-- If this is a new feature, please add 'RELNOTES[NEW]: <description>' here. If this is a breaking change, please add 'RELNOTES[INC]: <reason>' here. If this change should be mentioned in release notes, please add 'RELNOTES: <reason>' here. --> RELNOTES: None Commit ce5f8ba Co-authored-by: Ted Kaplan <tkaplan@roku.com>
[8.6.0] Fix visibility for implicit deps of parent rules (https://git… …hub.com/… (#28722) …/pull/28627) The visibility of a default value of an implicit dep in an extended rule should be checked relative to the definition of the rule that introduced it, which may not be the child rule. Fixes #28618 Closes #28627. PiperOrigin-RevId: 871303947 Change-Id: I0027e277dc9f01396fa4674297d2a73e1e9d257e <!-- Thank you for contributing to Bazel! Please read the contribution guidelines: https://bazel.build/contribute.html --> ### Description <!-- Please provide a brief summary of the changes in this PR. --> ### Motivation <!-- Why is this change important? Does it fix a specific bug or add a new feature? If this PR fixes an existing issue, please link it here (e.g. "Fixes #1234"). --> ### Build API Changes <!-- Does this PR affect the Build API? (e.g. Starlark API, providers, command-line flags, native rules) If yes, please answer the following: 1. Has this been discussed in a design doc or issue? (Please link it) 2. Is the change backward compatible? 3. If it's a breaking change, what is the migration plan? --> No ### Checklist - [ ] I have added tests for the new use cases (if any). - [ ] I have updated the documentation (if applicable). ### Release Notes <!-- If this is a new feature, please add 'RELNOTES[NEW]: <description>' here. If this is a breaking change, please add 'RELNOTES[INC]: <reason>' here. If this change should be mentioned in release notes, please add 'RELNOTES: <reason>' here. --> RELNOTES: None Commit a16489f --------- Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>
PreviousNext