Description of the feature request:
Same problem as #28930 : we need to create .mdx docs for the upcoming 9.1 release.
IIRC most of the docs changes are not part of the 9.x branch, so we probably need to run the old .md docs through the docs2mdx pipeline at HEAD, then use Gemini CLI to fix the various syntax errors and bring back custom header IDs.
Which category does this issue belong to?
No response
What underlying problem are you trying to solve with this feature?
No response
Which operating system are you running Bazel on?
No response
What is the output of bazel info release?
No response
If bazel info release returns development version or (@non-git), tell us how you built Bazel.
No response
What's the output of git remote get-url origin; git rev-parse HEAD ?
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
Description of the feature request:
Same problem as #28930 : we need to create .mdx docs for the upcoming 9.1 release.
IIRC most of the docs changes are not part of the 9.x branch, so we probably need to run the old .md docs through the docs2mdx pipeline at HEAD, then use Gemini CLI to fix the various syntax errors and bring back custom header IDs.
Which category does this issue belong to?
No response
What underlying problem are you trying to solve with this feature?
No response
Which operating system are you running Bazel on?
No response
What is the output of
bazel info release?No response
If
bazel info releasereturnsdevelopment versionor(@non-git), tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse HEAD?Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response