-
Notifications
You must be signed in to change notification settings - Fork 16.4k
[AIRFLOW-3193] Pin docker requirement version #4130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
|
AIRFLOW-3203 linked to #4049. |
Codecov Report
@@ Coverage Diff @@
## master #4130 +/- ##
==========================================
+ Coverage 76.66% 76.67% +<.01%
==========================================
Files 199 199
Lines 16212 16212
==========================================
+ Hits 12429 12430 +1
+ Misses 3783 3782 -1
Continue to review full report at Codecov.
|
|
Hi @ashb , would you mind to add this commit into 1.10.1? Understand that my PR #4049 ([AIRFLOW-3203] Fix DockerOperator & some operator test) is already cherry-picked into branch v1-10-test. The change made in that PR is partially meant to address a breaking change in Python package Cheers. |
|
@XD-DENG Ah cool. will do! |
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded actually. Therefore, the requirements config should upgrade also to avoid potentially misleading.
Since the change of AIRFLOW-3203, the dockerpy client has upgraded
actually. Therefore, the requirements config should upgrade also to
avoid potentially misleading.
@XD-DENG @Fokko
Make sure you have checked all steps below.
Jira
Description
Tests
Commits
Documentation
Code Quality
flake8