bazelbuild / bazelbuild/bazel

New deprecation warnings coming from Bazel internals in Bazel@HEAD

Open
#25,915 8 comments 0 reactions 2 assignees Claimed by @gregestren View on GitHub
P2 team-Configurability type: bug
Dominant language
Java
Stars
25.8k
Forks
4.6k
Avg merge
2d 20h
Merged PRs (30d)
72

Description

### Description of the bug:

These 2 warnings appear when building with HEAD

```
WARNING: /home/limdor/.cache/bazel/_bazel_limdor/7847781caf1fd5388b007bf353d8df72/external/bazel_tools/src/conditions/BUILD:149:15: in config_setting rule @@bazel_tools//src/conditions:host_windows_arm64_constraint: select() on host_cpu is deprecated. Use platform constraints instead: https://bazel.build/docs/configurable-attributes#platforms.
WARNING: /home/limdor/.cache/bazel/_bazel_limdor/7847781caf1fd5388b007bf353d8df72/external/bazel_tools/src/conditions/BUILD:144:15: in config_setting rule @@bazel_tools//src/conditions:host_windows_x64_constraint: select() on host_cpu is deprecated. Use platform constraints instead: https://bazel.build/docs/configurable-attributes#platforms.
```

They are not appearing in Bazel 8 LTS. The user is not able to do anything because they are coming from Bazel internals.

They were introduced by https://github.com/bazelbuild/bazel/commit/eec052436a3f8e8f0f715128ec26964b331fe7f5

### Which category does this issue belong to?

_No response_

### What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Build https://github.com/limdor/accu-2025/tree/9291a9de3784a59d00f05e676901e9b5dba6853a with Bazel@HEAD

### Which operating system are you running Bazel on?

Ubuntu 24.04

### What is the output of `bazel info release`?

development version

### If `bazel info release` returns `development version` or `(@non-git)`, tell us how you built Bazel.

Release from this version
https://github.com/bazelbuild/bazel/commit/eec052436a3f8e8f0f715128ec26964b331fe7f5

### What's the output of `git remote get-url origin; git rev-parse HEAD` ?

```text

```

### If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.

https://github.com/bazelbuild/bazel/commit/eec052436a3f8e8f0f715128ec26964b331fe7f5

### Have you found anything relevant by searching the web?

https://github.com/bazelbuild/bazel/issues/24751 but that is just a feature request mentioning similar warnings

### Any other information, logs, or outputs that you want to share?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.