Skip to content

Conversation

@potiuk
Copy link
Member

@potiuk potiuk commented May 11, 2025

…not pypi (#50459)

We do not need to publish sphinx-airflow-theme in PyPI - we can simply install the package directly from the wheel file published during main build of the airflow-site - this way we will always use the latest "main" version of the theme and we have no need to publish such newer versions of packages to PyPI.

This means that any committer can modify site theme and build it in sites and after merging to main, the theme will be used automatically from there.
(cherry picked from commit eb194c9)


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

…not `pypi` (apache#50459)

We do not need to publish sphinx-airflow-theme in PyPI - we can
simply install the package directly from the wheel file published
during `main` build of the `airflow-site` - this way we will always
use the latest "main" version of the theme and we have no need
to publish such newer versions of packages to PyPI.

This means that any committer can modify site theme and build it in
sites and after merging to main, the theme will be used automatically
from there.
(cherry picked from commit eb194c9)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
@potiuk potiuk merged commit 6843b3d into apache:v3-0-test May 11, 2025
50 checks passed
@potiuk potiuk deleted the backport-eb194c9-v3-0-test branch May 11, 2025 20:15
kaxil pushed a commit that referenced this pull request Jun 3, 2025
…not `pypi` (#50459) (#50465)

We do not need to publish sphinx-airflow-theme in PyPI - we can
simply install the package directly from the wheel file published
during `main` build of the `airflow-site` - this way we will always
use the latest "main" version of the theme and we have no need
to publish such newer versions of packages to PyPI.

This means that any committer can modify site theme and build it in
sites and after merging to main, the theme will be used automatically
from there.
(cherry picked from commit eb194c9)
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.

1 participant