kaxil opened a new pull request, #69478: URL: https://github.com/apache/airflow/pull/69478
A provider's docs index page listed only *cross-provider* extras -- extras that install another Airflow provider -- under "Optional cross provider package dependencies". A provider's plain-PyPI optional extras had no rendering path in the docs at all. For `common-ai` that left `anthropic`, `bedrock`, `openai`, `mcp`, `code-mode`, `langchain`, `llamaindex`, `pdf`, `docx` (and more) undocumented; for `amazon`, extras like `aiobotocore`, `s3fs`, and `pandas`. This adds an "Optional dependencies" section to the provider index template that renders the full extras table, so every extra a provider declares in `[project.optional-dependencies]` is documented alongside its dependencies and a `pip install pkg[extra]` example. ## Why this shape The optional-dependencies table and its Jinja context (`OPTIONAL_DEPENDENCIES`, `OPTIONAL_DEPENDENCIES_TABLE_RST`) already existed and are already rendered by the PyPI **README** template (added in #55280). The docs-site **index** template was simply never given the section, so this reuses the exact same computed context -- no new data plumbing. It sits alongside the existing "Optional cross provider package dependencies" table, which stays because it links out to the other providers' docs. This mirrors how the README already renders both tables. ## Rollout Provider `index.rst` files are regenerated at release time (`prepare-provider-documentation`), not on commit -- no pre-commit hook or PR CI check regenerates or diff-gates them. I regenerated `common-ai`'s index now so the section is visible immediately; every other provider picks it up automatically at its next release-docs regeneration, which keeps this PR's diff scoped to the one provider rather than churning 100+ files. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
