Skip to content

Conversation

@Lee-W
Copy link
Member

@Lee-W Lee-W commented Nov 29, 2024

Why

as stated in

``none_failed_or_skipped`` trigger rule has been deprecated
, this should be removed

What

remove deprecated TriggerRule.NONE_FAILED_OR_SKIPPED


^ 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 newsfragments.

@Lee-W Lee-W self-assigned this Nov 29, 2024
@Lee-W Lee-W added the airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes label Nov 29, 2024
@Lee-W Lee-W force-pushed the remove-deprecated-trigger-rules branch 2 times, most recently from e5e7cec to 6a35286 Compare November 29, 2024 15:57
@Lee-W Lee-W force-pushed the remove-deprecated-trigger-rules branch from 6a35286 to 477fdf0 Compare November 30, 2024 01:44
@shahar1 shahar1 merged commit 348181b into apache:main Nov 30, 2024
97 checks passed
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
…che#44475)

* refactor(trigger_rule): remove deprecated NONE_FAILED_OR_SKIPPED

* docs(newsfragments): add 44475.significant.rst
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

airflow3.0:breaking Candidates for Airflow 3.0 that contain breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants