Prepares provider release after PIP 21 compatibility #15576
Conversation
|
I would love to release those providers so that we can release PIP 21- compliant Airflow 2.0.3 |
|
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*. |
|
The Workflow run is cancelling this PR. It has some failed jobs matching ^Pylint$,^Static checks,^Build docs$,^Spell check docs$,^Provider packages,^Checks: Helm tests$,^Test OpenAPI*. |
e7d630b to
1bbf6b8
Compare
|
I'd love to release those :) |
64b7bd0 to
b51e571
Compare
This PR updates changelog and bumps version of providers to be released after we reached PIP 21 compatibility. It is necessary for two reasons: 1) We need it in order to get constraints for PyPI released providers to be updated automatically (PIP 21 conflicts master airflow with few released providers 2) We want to release Airflow 2.0.3 which will be PIP 21 installable with those providers.
b51e571 to
8c7dba3
Compare
|
The PR is likely OK to be merged with just subset of tests for default Python and Database versions without running the full matrix of tests, because it does not modify the core of Airflow. If the committers decide that the full tests matrix is needed, they will add the label 'full tests needed'. Then you should rebase to the latest master or amend the last commit of the PR, and push it with --force-with-lease. |
This PR updates changelog and bumps version of providers to be
released after we reached PIP 21 compatibility. It is necessary
for two reasons:
We need it in order to get constraints for PyPI released
providers to be updated automatically (PIP 21 conflicts master
airflow with few released providers
We want to release Airflow 2.0.3 which will be PIP 21 installable
with those providers.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code change, 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 UPDATING.md.