bugraoz93 opened a new pull request, #67651:
URL: https://github.com/apache/airflow/pull/67651
* [airflow-ctl-v0-1-test] Allow remote version check without authentication
(#65099) (#65904)
* fix(cli): allow remote version check without local config file
* fix(cli): introduce NO_AUTH client
* test(cli): add unit test for no-auth commands (cherry picked from commit
80cefdeff0358cbae67cd66bf5a0c20cb7e9d550)
* [airflow-ctl-v0-1-test] use existing safe_load function in airflowctl
utils to load help texts (#65841) (#65903)
(cherry picked from commit ad213e0)
* [airflow-ctl-v0-1-test] airflowctl: Send backfill create and dry-run
payloads as JSON (#65158) (#65937)
(cherry picked from commit ec8977cc2c562b3b3a4feb81041bb572a19183ea)
* Bump uv floor to 0.11.8, override cooldown for uv (#66042) (#66057)
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 dbfc27de982226cb325c7c6d4cb2ccfab946b6c5)
* [airflow-ctl-v0-1-test] Align Dag capitalization from "DAG" to "Dag" 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.
* [airflow-ctl/v0-1-test] Increment version of airflowctl for RC (#67295)
(#67384)
* Increment version of airflowctl for RC
* Change airflow-core usage for ctl
* Change airflow-core usage for ctl and amend installation in docker
* Prepare airflowctl for tests in CI
* Amend install airflow and provider to cover airflowctl (cherry picked from
commit 336a1199a1c9200d0bbb49f07477bdd24fc222d1)
* [airflow-ctl/v0-1-test] airflowctl: make required CLI params positional,
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 ffa426b64d7d99a66482b817887ee74d399824c4)
* [airflow-ctl/v0-1-test] Add dags next execution command #66172 (#66188)
(#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 6748ed8c45a8cb73ca8c31e711557012db0a30fc.
* Update help text Dag definition
---------
(cherry picked from commit 16ad4794f5a6c70480de7b137561f7f1bcdc2735)
* Sync main to backport branch for airflowctl (#67559)
* [airflow-ctl/v0-1-test] Add airflowctl 0.1.5 release notes (#67562)
(#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 1a1c145bc0a8c310d3027194395eda722d588d65)
---------
<!-- SPDX-License-Identifier: Apache-2.0
https://www.apache.org/licenses/LICENSE-2.0 -->
<!--
Thank you for contributing!
Please provide above a brief description of the changes made in this pull
request.
Write a good git commit message following this guide:
http://chris.beams.io/posts/git-commit/
Please make sure that your code changes are covered with tests.
And in case of new features or big changes remember to adjust the
documentation.
Feel free to ping (in general) for the review if you do not see reaction for
a few days
(72 Hours is the minimum reaction time you can expect from volunteers) - we
sometimes miss notifications.
In case of an existing issue, reference it using one of the following:
* closes: #ISSUE
* related: #ISSUE
-->
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [ ] Yes (please specify the tool below)
<!--
Generated-by: [Tool Name] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
-->
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
