srchilukoori opened a new pull request, #65840:
URL: https://github.com/apache/airflow/pull/65840
## Summary
- Vendors `sphinx_airflow_theme` (v0.3.9) from `apache/airflow-site` into
`docs-theme/` as a uv workspace member
- Replaces the remote `.whl` URL dependency with a local workspace dependency
- Enables local theme development without a publish-download cycle
Closes: #45576
## Changes
- **`docs-theme/`**: Vendored theme source (templates, static assets,
pre-built `_gen/` CSS/JS/fonts) from `apache/airflow-site`
- **`pyproject.toml`**: Added `docs-theme` to `[tool.uv.workspace]` members
and `sphinx-airflow-theme` to `[tool.uv.sources]`
- **`devel-common/pyproject.toml`**: Changed `sphinx-airflow-theme` from
`.whl` URL to standard version specifier (`>=0.3.9`)
- **`selective_checks.py`**: Added `^docs-theme` pattern to `DOC_FILES`
group so theme changes trigger docs CI builds
- **`upgrade_important_versions.py`**: Disabled URL-based theme version
fetching (now workspace-managed)
- **`.pre-commit-config.yaml`**: Excluded
`docs-theme/sphinx_airflow_theme/static/_gen/` from codespell and
inclusive-language checks (vendored third-party minified JS)
- **`dev/breeze/tests/test_theme_workspace.py`**: Smoke tests verifying
workspace wiring, source files, and static assets
## Motivation
As described in #45576, modifying the Sphinx docs theme currently requires
building and publishing a `.whl` to `airflow.apache.org` before changes can be
tested against Airflow docs. This makes theme development and Sphinx upgrades
unnecessarily difficult.
Adding the theme as a uv workspace member means `uv sync` resolves it from
the local `docs-theme/` directory. Editing a template and rebuilding docs
immediately reflects the change — no publish cycle needed.
## Was generative AI tooling used to co-author this PR?
Yes, Claude
--
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]
