Clone this repo:
  1. a4fd8e5 Add feature for `execution_requirements` on `ctx.actions.write` (#128) by Fabian Meumertzheim · 14 days ago upstream/main
  2. 206625f chore(deps): update dependency protobuf to v33.5 (#127) by renovate[bot] · 2 weeks ago
  3. b24b3c3 Don't open BCR PRs as drafts (#126) by Fabian Meumertzheim · 2 weeks ago
  4. a92343f Migrate to the Publish to BCR workflow (#125) by Fabian Meumertzheim · 2 weeks ago v1.40.0 v1.41.0
  5. ac482fd chore: generate stardocs on releases (#116) by Alex Eagle · 2 weeks 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.