airflow-ctl 0.1.5: test to stable - #67294
Merged
Merged
Conversation
Pins `[tool.uv] required-version` (and the matching marker-tagged constants in breeze) to 0.11.8 across the root and the three workspace members that carried their own (stale) floor (`airflow-core`, `airflow-ctl`, `dev/mypy` — all previously `>=0.6.3`). The bump picks up the timestamp-elision fix from astral-sh/uv#19022 (closes astral-sh/uv#18708 — relative `exclude-newer` no longer writes a churning timestamp into uv.lock that two branches collide on). Drops uv's per-package cooldown to "12 hours" in both [tool.uv.exclude-newer-package] and [tool.uv.pip.exclude-newer-package]; without the override the project-wide 4-day window blocks a freshly-released uv from being adopted as the floor. The override is flagged "REMOVE BY 2026-05-01" — once 0.11.8 is older than the global 4-day cooldown the override is redundant. Bumps AIRFLOW_UV_VERSION across Dockerfiles, breeze constants, and the image-args doc to match. The `# sync-uv-min-version`-tagged test fixtures were auto-rewritten by the prek hook of the same name. uv.lock confirms the upstream fix is engaged: `exclude-newer` reads as the no-op `0001-01-01T00:00:00Z` placeholder. (cherry picked from commit dbfc27d)
…for airflow-ctl/ (#66112) (#66217) Backport of #66112. Conflicts resolved by keeping v0-1-test base for unrelated divergences (only_new field, validate_model, is_backfillable property, DAGRunCollectionResponse multi-line docstring) and applying only the DAG -> Dag description-text changes — feature-related lines absent in v0-1-test were not introduced. Co-authored-by: hojeong park <parkhj062@gmail.com>
bugraoz93
requested review from
amoghrajesh,
ashb,
bbovenzi,
choo121600,
dheerajturaga,
ephraimbuddy,
gopidesupavan,
guan404ming,
jason810496,
jedcunningham,
jscheffl,
pierrejeambrun,
potiuk,
rawwar,
ryanahamilton,
shubhamraj-git and
vatsrahul1001
as code owners
May 21, 2026 18:22
boring-cyborg
Bot
added
area:airflow-ctl
area:API
potiuk
approved these changes
May 22, 2026
…al, keep optional as --flag (#66768) (#67387) * airflowctl: make required CLI params positional, keep optional as --flag Auto-generated commands such as ``airflowctl dags get-details`` now accept required primitive parameters positionally: airflowctl dags get-details my_dag_id instead of the previous ``--dag-id my_dag_id`` form. Optional parameters and booleans keep the ``--flag`` form. This follows the dev-list lazy consensus on airflowctl parameter style. A parameter is considered required when the operation method declares it without a default and without ``| None`` in its annotation. Datamodel- expanded body fields are unaffected — they are not "parameters of the operation method" in this sense and continue to use ``--flag``. * tests: tmp_path fixture for command-factory; positional form for integration tests Two follow-ups to the positional-required-args change: - ``TestCommandFactory._save_temp_operations_py`` previously wrote a shared ``test_command.py`` in cwd; under pytest-xdist that file is raced by workers, so ``next(arg for arg in jobs_list_args if ...)`` in one test could see content written by another and raise ``StopIteration``. Helper now takes the per-test ``tmp_path`` and returns the full path. The classmethod ``teardown_method`` that removed the shared file is no longer needed (pytest auto-cleans ``tmp_path``). - The Airflow CTL PROD-image integration tests still invoked converted parameters with the old ``--flag value`` form (e.g. ``--variable-key=X``, ``--section X --option Y``, ``--dag-id=example_bash_operator``). Updated each occurrence to the positional form that the regenerated CLI now expects. Optional parameters (``--logical-date``, ``--run-after``, ``--is-paused``, ``--state``, ``--limit``, etc.) stay as ``--flag``. --------- (cherry picked from commit ffa426b) Signed-off-by: 1fanwang <1fannnw@gmail.com> Co-authored-by: Stefan Wang <1fannnw@gmail.com>
… (#67386) * Add airflowctl dags next-execution command #66172 * Add generated OpenAPI spec and UI types * Revert "Add generated OpenAPI spec and UI types" This reverts commit 6748ed8. * Update help text Dag definition --------- (cherry picked from commit 16ad479) Co-authored-by: Haseeb Malik <118837269+haseebmalik18@users.noreply.github.com>
Contributor
Author
|
Will merge after backporting release notes :) |
…67576) * Add airflowctl 0.1.5 release notes * Add double backticks * Apply suggestions from code review * Amend release notes without backports and duplicates, add misc as commented visibility --------- (cherry picked from commit 1a1c145) Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 31, 2026
The "airflow-ctl 0.1.5: test to stable" sync (apache#67294) copied main's airflow-core/pyproject.toml metadata onto this branch without the matching sources. Three leftovers stayed behind: - the distribution version became 3.3.0 while airflow-core/src/airflow/__init__.py stayed 3.2.1 - the Task SDK requirement became >=1.3.0,<1.4.0 while task-sdk on this branch is 1.2.1 - a force-include and a shared_distributions entry appeared for apache-airflow-shared-state, which has no shared/state folder here Once CI actually started running on this branch, the CI image build failed pip check on the resulting triangle: apache-airflow 3.2.1 has requirement apache-airflow-core==3.2.1, but you have apache-airflow-core 3.3.0 apache-airflow-core 3.3.0 has requirement apache-airflow-task-sdk<1.4.0,>=1.3.0, but you have 1.2.1 apache-airflow-task-sdk 1.2.1 has requirement apache-airflow-core<3.3.0,>=3.2.0, but you have 3.3.0 Realign the metadata with the sources that are on the branch, which is what check-version-consistency and check-shared-distributions-usage already expect, and refresh uv.lock, which had drifted from the same sync.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 31, 2026
The same test-to-stable sync (apache#67294) repointed the mypy-airflow-ctl hook at ../scripts/ci/prek/run_mypy_full_dist_local_venv_or_breeze_in_ci.py, which only exists on main. On this branch prek dies before mypy runs: error: Failed to run hook `mypy-airflow-ctl` caused by: Run command `python hook` failed caused by: No such file or directory (os error 2) Point it back at mypy_local_folder.py, which is what airflow-core, task-sdk, devel-common and dev/scripts all use on this branch.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 31, 2026
The "airflow-ctl 0.1.5: test to stable" sync (apache#67294) copied main's airflow-core/pyproject.toml metadata onto this branch without the matching sources. Three leftovers stayed behind: - the distribution version became 3.3.0 while airflow-core/src/airflow/__init__.py stayed 3.2.1 - the Task SDK requirement became >=1.3.0,<1.4.0 while task-sdk on this branch is 1.2.1 - a force-include and a shared_distributions entry appeared for apache-airflow-shared-state, which has no shared/state folder here Once CI actually started running on this branch, the CI image build failed pip check on the resulting triangle: apache-airflow 3.2.1 has requirement apache-airflow-core==3.2.1, but you have apache-airflow-core 3.3.0 apache-airflow-core 3.3.0 has requirement apache-airflow-task-sdk<1.4.0,>=1.3.0, but you have 1.2.1 apache-airflow-task-sdk 1.2.1 has requirement apache-airflow-core<3.3.0,>=3.2.0, but you have 3.3.0 Realign the metadata with the sources that are on the branch, which is what check-version-consistency and check-shared-distributions-usage already expect, and refresh uv.lock, which had drifted from the same sync.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Jul 31, 2026
The same test-to-stable sync (apache#67294) repointed the mypy-airflow-ctl hook at ../scripts/ci/prek/run_mypy_full_dist_local_venv_or_breeze_in_ci.py, which only exists on main. On this branch prek dies before mypy runs: error: Failed to run hook `mypy-airflow-ctl` caused by: Run command `python hook` failed caused by: No such file or directory (os error 2) Point it back at mypy_local_folder.py, which is what airflow-core, task-sdk, devel-common and dev/scripts all use on this branch.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Aug 3, 2026
The test-to-stable sync (apache#67294) copied airflowctl's generated datamodels from main, so they describe Airflow 3.3's API while this branch ships core 3.2.1. Two consequences, both red once CI started running here: - generate-airflowctl-datamodels regenerates from ../airflow-core/src/airflow/api_fastapi and fails on any drift, so Static checks could never pass - the models required is_backfillable and timetable_periodic, which apache#64644 added in 3.3.0, so every single-object Dag response failed validation against this branch's own PROD image: ValidationError: 2 validation errors for DAGResponse is_backfillable Field required timetable_periodic Field required Run the hook to bring the models back in line with the spec on this branch. This drops 14 model classes that no airflowctl code or test references, plus the 3.3-only fields above. Note RELEASE_NOTES.rst credits "Add ``is_backfillable`` property to DAG API responses (apache#64644)" to airflowctl 0.1.5, but apache#64644 touches only airflow-core -- that line is sync noise, not a client feature.
Lee-W
added a commit
to astronomer/airflow
that referenced
this pull request
Aug 3, 2026
The test-to-stable sync (apache#67294) copied airflowctl's generated datamodels from main, so they describe Airflow 3.3's API while this branch ships core 3.2.1. Two consequences, both red once CI started running here: - generate-airflowctl-datamodels regenerates from ../airflow-core/src/airflow/api_fastapi and fails on any drift, so Static checks could never pass - the models required is_backfillable and timetable_periodic, which apache#64644 added in 3.3.0, so every single-object Dag response failed validation against this branch's own PROD image: ValidationError: 2 validation errors for DAGResponse is_backfillable Field required timetable_periodic Field required Run the hook to bring the models back in line with the spec on this branch. This drops 14 model classes that no airflowctl code or test references, plus the 3.3-only fields above. Note RELEASE_NOTES.rst credits "Add ``is_backfillable`` property to DAG API responses (apache#64644)" to airflowctl 0.1.5, but apache#64644 touches only airflow-core -- that line is sync noise, not a client feature.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Sync airflow-ctl/v0-1-test into airflow-ctl/v0-1-stable for the airflow-ctl 0.1.5 release.
Need backport of (depends): #67295 merged to backport branch. Then it will merge. But ready for review as the only version will lend