When switching the Bazel version, the bazel_features_version repo generated by

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• chore(deps): update dependency bazel to v7.2.1

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• chore(deps): update dependency bazel_skylib to v1.7.1
• chore(deps): update dependency io_bazel_stardoc to v0.7.0

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

This mostly make it easier to generate docs for projects that depend on bazel-features and use bzl_library for their bzl libraries, but is also generally useful for bzl files that are libraries and need their dependencies modeled.

Without such a feature, projects have to manually define a bzl_library target to include the sources, which is just boilerplate:

bzl_library(
    name = "bazel_features_bzl",
    srcs = ["@bazel_features//:bzl_files"],
)

Currently, there's an external repository with bazel version stamped inside .bzl file to allow access to bazel version from non-repository contexts.

This is unnecessary if bazel_features is being called from a repository context where bazel-version is accessible therefore making the external version repository unnecessary.

when I use bazel_features in bazel 5.
I meet the following error
external/bazel_features/private/util.bzl:1:6: Unable to find package for @bazel_features_version//:version.bzl: The repository '@bazel_features_version' could not be resolved: Repository '@bazel_features_version' is not defined.