[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 https://github.com/bazelbuild/bazel/commit/79fb84383bd92e0d53d1caaaab23f8578bc1259b and https://github.com/bazelbuild/bazel/commit/246ea9891e49909222be085f25cb70e0d21554bf --------- Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

Release 10.0.0-pre.20260322.2 (2026-04-01) Baseline: f00741106467895a4ae70206b00f122f2ebbbc1c 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: f3ab7948c2dff519f8228890b3878a5586d2b723 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: d67b13a5d8e8fa2715ae8ebbd4a0ca1b8c1d495a Cherry picks: + eb3941da848addebd7ebe530771a5839e8f9dfa3: Automated rollback of commit 4f793a81b502b345e47b55b09216430af0fb08f0. + 51907c4773cd91342f8f39f1e6f92938e6372784: Release 10.0.0-pre.20260308.2 (2026-03-13) + fc4340c57c203e0cb7f93750dd3ec4d67d7eb358: Release 10.0.0-pre.20260308.2 (2026-03-13) + 7a135942ed0da98456dafff07130e5df5d871d9e: Release 10.0.0-pre.20260308.2 (2026-03-13) + a933bce49ec0cc3a0463a6e7691b1d10a4d85849: Release 10.0.0-pre.20260308.2 (2026-03-13) + 9b133bc7d7c0e2514cf83ef7a922ec812c2247d9: Release 10.0.0-pre.20260308.2 (2026-03-13) + 9bc159f6cc9c2e9205d259123513bd58abd82e46: Release 10.0.0-pre.20260308.2 (2026-03-13) + e0f314633c0b4c2e28202ad757e7c4c80420459a: Release 10.0.0-pre.20260308.2 (2026-03-14) + 9ef180ef79914603d56088335993ce90a78acc6d: Release 10.0.0-pre.20260308.2 (2026-03-16) + 704831db809db3a7c45b75e88866c6dea2459d4b: Release 10.0.0-pre.20260308.2 (2026-03-16) + 2aebc4d79e03f8347d3dcefdf7c6d0b83144d609: Release 10.0.0-pre.20260308.2 (2026-03-16) + 8a81d0bb0eeaab8b3a5a33e2988d92322ca5f4cb: Release 10.0.0-pre.20260308.2 (2026-03-16) Incompatible changes: - `--incompatible_check_testonly_for_output_files` has been flipped. See https://github.com/bazelbuild/bazel/issues/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 9.0.1 (2026-03-10) Release Notes:

Release 10.0.0-pre.20260223.3 (2026-03-06) Baseline: 6dd6396737cf953159079cee20355ba6123c934b Cherry picks: + fd860b00f2614ca0697fd33f8741db8f32340358: 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: https://github.com/bazelbuild/bazel/commit/f0ec350d5c2fba8a31d786aba9fbff849b944dcf Co-authored-by: Yun Peng <pcloudy@google.com>

Release 8.6.0 (2026-02-26) Release Notes:

[8.6.0] Only use workspace facts for validation with --lockfile_mode=error (h… (#28766) …ttps://github.com/bazelbuild/bazel/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 https://github.com/bazelbuild/bazel/commit/ce5f8ba8a7d3741c2e2fd3fe9a8b8aaa25de4ef6 Co-authored-by: Ted Kaplan <tkaplan@roku.com>

[8.6.0] Fix visibility for implicit deps of parent rules (https://github.com/… (#28722) …bazelbuild/bazel/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 https://github.com/bazelbuild/bazel/commit/a16489f96bb436b6e6abc350a4f38070bc7f1a6e --------- Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

Release 10.0.0-pre.20260211.1 (2026-02-18) Baseline: 6edc9a8b61395ca54794479d2e9fee47a68dd4b6 Important changes: - Labels in the main repo will now have a `repr` form that reliably evaluates back to themselves (that is, `repr(Label("@@//:foo")) == "Label(\"@@//:foo\")"`). - The `compatibility_level` and `max_compatibility_level` attributes of `module` in MODULE.bazel are now no-ops. Module maintainers should stop specifying those attributes and provide clear build time error messages and actionable migration paths when making major breaking changes. This release contains contributions from many people at Google, as well as Damian Banki, dependabot[bot], Fabian Meumertzheim, giria660.

Release 10.0.0-pre.20260204.1 (2026-02-12) Baseline: 0a2574e8a302d1edc91a83fee825961a090e1573 Important changes: - Bazel now fails over immediately to mirror URLs if a TLS handshake error occurs. This release contains contributions from many people at Google, as well as ashutosh0x, Fabian Meumertzheim, Keith Smiley, Tyler French, Will Stranton.

[8.6.0] Force `rctx.{download_and,}extract` to create user-readable files (ht… (#28551) …tps://github.com/bazelbuild/bazel/pull/28531) Archives in the wild do sometimes contain non-readable files, but other tools work around this and thus mask their brokenness. Context: https://bazelbuild.slack.com/archives/CDCMRLS23/p1770213515354229 Closes #28531. PiperOrigin-RevId: 865960367 Change-Id: I7273eb983d63d6960d184764cec5040bba77b2c2 Commit https://github.com/bazelbuild/bazel/commit/0bb7836a42a8c26f8730a4b8b4156c6d0768b718 Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>

Release 10.0.0-pre.20260128.2 (2026-02-06) Baseline: 3ad9562ae006151d40a0ebcc90b84889888c2111 This release contains contributions from many people at Google, as well as Alex Eagle, Benjamin Peterson, Fabian Meumertzheim, Paul Tarjan.

Release 10.0.0-pre.20260120.1 (2026-01-29) Baseline: cc1e0a6ba439764fea48e1f8035419aa44313f05 Incompatible changes: - The `config_setting`s `@bazel_tools//src/conditions:{host_windows,remote}` have been removed. Toolchains are usually a better fit as they don't depend on the configuration of the host machine running Bazel and/or fixed execution modes. Important changes: - Reporting of cached test results can now be suppressed with `--test_summary=short_uncached` or `--test_summary=detailed_uncached`. This release contains contributions from many people at Google, as well as Benjamin Peterson, Fabian Meumertzheim, Jordan Mele, Kapunahele Wong, Keith Smiley, Yagiz Nizipli.

Release 10.0.0-pre.20260114.1 (2026-01-22) Baseline: a4e9e9774d3266b829de7e0b7e7cd75791ca3333 Initial release.

Release 6.6.0 (2026-01-21) Baseline: d2daa9b6fed3f38bf8e8cce90a0d17ea945c1ab7 Release Notes: + Release 6.5.0 (2024-01-23) + Fixes for using recent Xcodes and macOS 26 (#27463) + Match postsubmit jobs with presubmit (#28193) Acknowledgements: This release contains contributions from many people at Google, as well as Mike Bland.

Release 9.0.0 (2026-01-20) Release Notes:

Release 10.0.0-pre.20260112.1 (2026-01-16) Baseline: 7111cbfcecdd3bda3e4beedd8b59dc93d3652607 Cherry picks: + 76166fca04ca8fdf6d87b3a2a7cf60da6ca8145b: Use the hermetic python toolchain for Bazel Important changes: - The new `package_relative_label` function on the rule context (`ctx`) can be used to turn a user-provided label string into a `Label` relative to the target that is currently being analyzed (where `Label(...)` would return a `Label` relative to the `.bzl` file containing the call). This release contains contributions from many people at Google, as well as Alex Eagle, Alex O'Brien, Carmen Chui, Damian Banki, dependabot[bot], Fabian Meumertzheim, George Gensure, google-labs-jules[bot], jade.

Release 10.0.0-pre.20260104.1 (2026-01-15) Baseline: 571ed6a26de82b041dedb6d30ff816c97c68e79a Cherry picks: + 1f2624a0b0a55f692ef019c731c0a9cb8cca0638: Cherry picks for 10.0.0-pre.20260104.1 (#28313) Important changes: - C static libraries can now elide backwards reference warnings (if linking with LLD and such warnings are enabled) if the `warn_backrefs_defined` feature is defined and enabled for the toolchain. This release contains contributions from many people at Google, as well as Alex Novak, Carmen Chui, Dan Katz, Fabian Meumertzheim, gampu, Keith Smiley.