…API is used to look up a DAG run
- Resolve compatibility issues and refactor `execution_date` to `logical_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
Resolve compatibility issues and refactor `execution_date` to `logical_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
Resolve compatibility issues and refactor `execution_date` to `logical_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
Resolve compatibility issues and refactor `execution_date` to `logical_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
Resolve compatibility issues and refactor `execution_date` to `logical_date`
- Resolve compatibility tests
- Correct import paths after rebase
- Address static checks
- Refactor `execution_date` to `logical_date`
- Add missing DAG files for tests
- Enhance GCP ML and CloudBuild tests using helpers for compatibility
- Fix mypy errors
- Miscellaneous fixes and removals of `execution_date`
More name changes and argument removal
Mass replace execution_date in arguments
Not finished, still many to go.
Mass replace execution_date in arguments
Not finished, still many to go.
Drop execution_date unique constraint on DagRun
The column has also been renamed to logical_date, although the Python
model is not changed. This allows us to not need to fix all the Python
code at once (we'll do that later), but still do the two changes in one
migration instead of two.
Fix compat tests
Fix compat tests
Fix compat test
Fix the tests
Fix compat tests
Fix compat tests
Fix compat tests
Fix compat tests
Fix compat tests
Fix compat tests
Fix static checks
Fix the pytest_plugin by refactor renaming execution_date to logical_date
Fix the pre-commit errors
Fix import paths after rebase
fix more compat tests
Fix the compat tests
Fix the compat tests
Fix the compat tests
Use test helpers in GCP MLEngine tests for compat
Using Airflow internals directly presents a problem when dealing with
compatibility in tests (since the same tests must run against Airflow 2
and 3). The helpers already handle this well, so we should use them.
Use test helpers in GCP CloudBuild tests for compat
Using Airflow internals directly presents a problem when dealing with
compatibility in tests (since the same tests must run against Airflow 2
and 3). The helpers already handle this well, so we should use them.
Mark db tests
Some compat code to make DAG.clear() still work
Remove unneeded test cases for compat code
Use test helpers in GCS-BQ tests for compat
Using Airflow internals directly presents a problem when dealing with
compatibility in tests (since the same tests must run against Airflow 2
and 3). The helpers already handle this well, so we should use them.
Fix tests and add missing dag_file for tests
Add missing dag_file for tests
Fix some provider/cncf compat on logical date
We should continue to use execution_date if the provider is run against 2.
Fix the cache import path
refactor rename execution_date, executionDate to logical_date, logicalDate respectively.
refactor rename execution_date, executionDate to logical_date, logicalDate respectively.
fix more tests
Fix more tests
Fix more tests
More fixes on removal of execution date
Fix more tests
fix more tests
Fix tests
Fix tests
Fix tests
fix the static checks
remove the migration
fix the tests
Fix migration file
Remove renaming execution date for SlaMiss
Remove execution_date and add logical date
Fix mypy errors
try-except for 2.x. for DagRun
Remove _DEPRECATION_REPLACEMENTS
More name changes and argument removal
Mass replace execution_date in arguments
Not finished, still many to go.
Mass replace execution_date in arguments
Not finished, still many to go.
Drop execution_date unique constraint on DagRun
The column has also been renamed to logical_date, although the Python
model is not changed. This allows us to not need to fix all the Python
code at once (we'll do that later), but still do the two changes in one
migration instead of two.