-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Add check for coerce_datetime to Airflow 2-1 compatibility check #22499
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
Add check for coerce_datetime to Airflow 2-1 compatibility check #22499
Conversation
|
CC: @lwyszomi -> this one will fail now so I will rebase after your PR is merged. |
|
This probably means RC2 for google provider? |
|
@potiuk thanks :) |
|
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
Not really. This is just 2.1+ compatibility problem and it has been already released so it is not a "regression" in the new release. BTW. It was actually me who introduced it here: 3728494 🤦 |
|
True. That was actually a teamwork :) |
766cf3d to
2a5d2df
Compare
Checking coerce_datetime presence (and also consolidating all 2.1 checks in a single pre-commit check).
2a5d2df to
10f108d
Compare

Checking coerce_datetime presence (and also consolidating all
2.1 checks in a single pre-commit check).
^ 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.