Skip to content

Conversation

@sc250072
Copy link

@sc250072 sc250072 commented Jul 1, 2025


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an 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 a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

dominikhei and others added 30 commits June 24, 2025 12:18
* Support no_status alias in TaskInstance state filter for REST API

* Allow 'no_status' state filter and include no_status in valid state list; skip date filters when filtering for null state

* Fix NULL-state filtering in get_mapped_task_instances by coalescing date fields

* Refactor datetime_range_filter_factory: coalesce only start_date and end_date filters

* Add a test
Pattern is The Premier Accelerator for Global Ecommerce
* Add a button to collapse/expand the information panel for better visualizing DAG

* remove transform of IconButton

* change Box width

* add translations for aria-label (en, zh-TW)

* change translations for zh-TW
This was removed in apache#50464, but we still need to do this step.
We need these, so fail early if they are missing (say, you missed
escaping a newline 😂).
These were not used and aren't part of public interface.
These isn't used in Airflow 3 and isn't part of public interface.
Had to todo earlier, resolved that.
This aren't used anymore -- these were initially part of AIP-44 but were missed during cleanup
Following the discussion in devlist - this PR adds description of
what kind of changes we cherry-pick:

https://lists.apache.org/thread/f3off4vtn2h6ctznjd5wypxvj1t38xlf
I removed SimpleTaskInstance in apache#52176 since it isn't used in Airflow 3. This caused failure in hybrid executors like `LocalKubernetesExecutor` and `CeleryKubernetesExecutor` -- which aren't suported in Airflow 3. Hence we can ignore mypy errors.
The apache#52187 added ignores in a bit wrong place due to auto-reformatting
* Add default conn name to asana provider operators

* Update tests
* allow to use any reference not only tag when publishing docs
* autocomplete destinations for publish-to-s3 command
apache#51952)

Co-authored-by: Jed Cunningham <jedcunningham@apache.org>
kyungjunleeme and others added 27 commits July 1, 2025 06:02
…e#52610)

* NEW: add conditional import for BaseOperator

* CHG: change import path
…adog` (apache#52583)

* Provider Migration: Replace BaseSensorOperator to Task SDK for datadog

* Apply suggestion from @kaxil

---------

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…apache#52577)

* Provider Migration: Replace BaseOperator to Task SDK for dingding

* Apply suggestion from @kaxil

---------

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…e with uv (apache#52612)

* Update app.py

Add follow_symlink for StaticFiels

* Update simple_auth_manager.py

add follow_symlink for StaticFiles
…e#52347)

* replace baseOperator to Task SDK

* fix version compat

* update imports
* Add regional support for google secret manager hook

* Change property name from location_id to location

* Remove backward compatibility comment.

* Fix static check failing
The dependency reports of ours will be different for:

* different python versions
* different constraint modes

We change the job to produce the reports into matrix of jobs
producing reports for all combinations of those.
…k_group`'s (apache#51556)

* Added same logic to @task_group as is in @task for mapping over invalid XCom arg

* Added same logic to @task_group as is in @task for mapping over invalid XCom arg

* Fixing linting
…che#52603)

* Update grpc BaseOperator imports for Airflow 3.0 compatibility

* Apply suggestions from code review

---------

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
…pache#52602)

* Update influxdb BaseOperator imports for Airflow 3.0 compatibility

* Apply suggestions from code review

---------

Co-authored-by: Kaxil Naik <kaxilnaik@gmail.com>
Our dependencies should be set in "upgrade to newer dependencies"
mode every time every single pyproject.toml changes - this is slower
as it triggers full builds with all versions but it also prevents some
errors when dependencies from one provider are impacting what will
be resolved in the CI image. As part of it - whenever we run the
dependency report with "source constraints" we use exactly the same
`uv sync` command as used during image build with "ugprade to
newer dependencies" - this way the report is more accurate as it
includes some dependencies from dev dependency groups that have
not been included in the current reports.
In apache#50715 we starting short-circuiting if we hit 5 iterations of no new
log messages. This works well, except in the scenario where there are no
log messages at all. ES log handler has it's own short-circuit for that
scenario, but it triggers based on time and that works out to ~7
iterations. Let's let ES have the first crack at it so the user gets a
better message.

Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
…vOperator` (apache#52287)

* Use `index_urls` when venv is created with `uv`

* Fix formatting

* Remove conditional creation of `pip.conf`

* Set Python package index for uv with environment variables

* Update documentation

* Fix unit tests
…pache#52623)

Co-authored-by: Natanel Rudyuklakir <natanelrudyuklakir@gmail.com>
…52635)

Pyarrow < 16.1.0 does not play well with numpy 2. Bumping it to
16.1.0 as minimum version should make compatibility tests to not
downgrade to versions that are not compoatible when numpy 2 is
already installed. It should also prevent our users from accidentally
downgrading pyarrow or not upgrading it when numpy is upgraded
to >= 2.0.0.
…ecks (apache#52644)

This came in to effect once we swapped to Py 3.10 as the minimum version.

This is inplace because of the ruff rule [UP038], and as we have discovered
(after changing it to this style in the first place) the docs for the rule
say:

> **Warning: This rule is deprecated and will be removed in a future release.**

So lets change it back

[UP038]:  https://docs.astral.sh/ruff/rules/non-pep604-isinstance/#deprecation
@sc250072 sc250072 merged commit f5c3501 into error_msg Jul 1, 2025
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.