Clone this repo:
  1. 9347245 Update bazel-contrib/publish-to-bcr action to v1.5.1 (#138) by renovate[bot] · 9 days ago upstream/main
  2. 5475721 Update bazel-contrib/setup-bazel action to v0.19.0 (#137) by renovate[bot] · 9 days ago
  3. 40f1a6d Add rules.platform_has_flags (#156) by Fabian Meumertzheim · 10 days ago v1.52.0
  4. f3f9e89 Recognize `refines_constraint_value` in Bazel 9.2.0 (#155) by Fabian Meumertzheim · 10 days ago
  5. 6b47801 Update dependency bazel to v9.3.0 (#153) by renovate[bot] · 10 days ago

Bazel Features

Use this to determine the availability of a Bazel feature in your ruleset. It works under the hood by comparing the Bazel version against a known range in which the feature is available. Example usage:

load("@bazel_features//:features.bzl", "bazel_features")
if bazel_features.toolchains.has_optional_toolchains:
    # Do something

The features.bzl file contains the list of features.

Accessing globals

References to global Starlark symbols that do not exist cause load time errors, which means that their availability in Bazel cannot be tested via a regular feature. Instead, use bazel_features.globals.<symbol>, which is <symbol> if the symbol is available and None else.

See globals.bzl for the list of symbols that can be checked for in this way.