The GitHub Actions job "Tests AMD" on 
airflow.git/remove-dev-dependencies-from-pypi-constraints has failed.
Run started by GitHub user potiuk (triggered by potiuk).

Head commit for run:
afcd0a29358dae827da31435801357477955c509 / Jarek Potiuk <[email protected]>
Remove dev dependencies from PyPI constraints.

Historically, `PyPI` constraints of airflow contained also the
development dependencies of Airflow - because it was not very easy
to separate and remove them from the "core" constraints.

This however might not be really needed and those dev tools could be
removed from PyPI constraints.

There are however certain consequences:

a) currently when we generate PyPi constraints we generally *know* that
the dependencies of ours have been tested at some point of time at
least when we released the provider - because potentially some of our
dev dependencies might limit some 3rd-party deps

b) if we remove devel deps when we generate the PyPI constraints this
**might** change - i.e. removal of development dependencies might
cause some of the transient dependencies to be upgraded to newer -
potentially incompatible versions. It's not very likely but possible.

This means that if we remove devel deps, there is a higher risk that
constraints published for users might contain dependency versions
that has never been tested in our CI.

Another option considered is to use a) and b) and remove the
dependencies missing in b) from a) - leaving the versions that were
matching the versions used during CI. This however has limited impact
on the users (just removes the "devel noise" from PyPI constraints
- and the noise that should not matter when installing airflow). And
it has anothe risk that some edge cases might kick-in. For example
there might be a case where our dependencies add or remove their
transient dependencies, which might change status of those from
devel to prod or the other way round. And it's quite a bit more
complex.

Report URL: https://github.com/apache/airflow/actions/runs/16681777935

With regards,
GitHub Actions via GitBox


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to