Skip to content

docs(howto): add optional feature loading guide - #4003

Merged
rickeylev merged 2 commits into
bazel-contrib:mainfrom
rickeylev:docs_loadable_symbols_usage
Aug 5, 2026
Merged

docs(howto): add optional feature loading guide#4003
rickeylev merged 2 commits into
bazel-contrib:mainfrom
rickeylev:docs_loadable_symbols_usage

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

Macro and rule authors need clear guidance on writing Bazel code that
remains compatible across multiple rules_python releases as new APIs are
introduced. Previously, using features.loadable_symbols, targets, and
version lacked dedicated documentation, making it harder for developers
to know how to use these feature-detection APIs.

Add a how-to guide (docs/howto/optional-feature-loading.md) showing
how to inspect //python:features.bzl and generate compatibility repo
rules, BUILD files, and macro version checks.

Add documentation showing how to use features.loadable_symbols,
features.targets, and features.version for multi-version compatibility
in macros, BUILD files, and repository rules.
@rickeylev
rickeylev requested a review from aignas as a code owner August 5, 2026 04:05
@rickeylev
rickeylev enabled auto-merge August 5, 2026 04:09
@rickeylev
rickeylev added this pull request to the merge queue Aug 5, 2026
Merged via the queue into bazel-contrib:main with commit a2bdf6b Aug 5, 2026
6 checks passed
@rickeylev
rickeylev deleted the docs_loadable_symbols_usage branch August 5, 2026 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants