Bump apache-airflow from 2.8.1 to 2.10.1

[dependabot[bot]]

Bumps apache-airflow from 2.8.1 to 2.10.1.

Release notes

Sourced from apache-airflow's releases.

Apache Airflow 2.10.1

Significant Changes

No significant changes.

Bug Fixes

• Handle Example dags case when checking for missing files (#41874)
• Fix logout link in "no roles" error page (#41845)
• Set end_date and duration for triggers completed with end_from_trigger as True. (#41834)
• DAGs are not marked as stale if the dags folder change (#41829)
• Fix compatibility with FAB provider versions <1.3.0 (#41809)
• Don't Fail LocalTaskJob on heartbeat (#41810)
• Remove deprecation warning for cgitb in Plugins Manager (#41793)
• Fix log for notifier(instance) without name (#41699)
• Splitting syspath preparation into stages (#41694)
• Adding url sanitization for extra links (#41680)
• Fix InletEventsAccessors type stub (#41607)
• Fix UI rendering when XCom is INT, FLOAT, BOOL or NULL (#41605)
• Fix try selector refresh (#41503)
• Incorrect try number subtraction producing invalid span id for OTEL airflow (#41535)
• Add WebEncoder for trigger page rendering to avoid render failure (#41485)
• Adding tojson filter to example_inlet_event_extra example dag (#41890)
• Add backward compatibility check for executors that don't inherit BaseExecutor (#41927)

Miscellaneous

• Bump webpack from 5.76.0 to 5.94.0 in /airflow/www (#41879)
• Adding rel property to hyperlinks in logs (#41783)
• Field Deletion Warning when editing Connections (#41504)
• Make Scarf usage reporting in major+minor versions and counters in buckets (#41900)
• Lower down universal-pathlib minimum to 0.2.2 (#41943)
• Protect against None components of universal pathlib xcom backend (#41938)

Doc Only Changes

• Remove Debian bullseye support (#41569)
• Add an example for auth with keycloak (#41791)

Apache Airflow 2.10.0

Significant Changes

Datasets no longer trigger inactive DAGs (#38891)

Previously, when a DAG is paused or removed, incoming dataset events would still trigger it, and the DAG would run when it is unpaused or added back in a DAG file. This has been changed; a DAG's dataset schedule can now only be satisfied by events that occur when the DAG is active. While this is a breaking change, the previous behavior is considered a bug.

... (truncated)

Changelog

Sourced from apache-airflow's changelog.

.. Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

.. http://www.apache.org/licenses/LICENSE-2.0

.. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

.. contents:: Apache Airflow Releases :local: :depth: 1

.. towncrier release notes start

Airflow 2.10.0 (2024-08-15)

Significant Changes ^^^^^^^^^^^^^^^^^^^

Datasets no longer trigger inactive DAGs (#38891) """""""""""""""""""""""""""""""""""""""""""""""""

Previously, when a DAG is paused or removed, incoming dataset events would still trigger it, and the DAG would run when it is unpaused or added back in a DAG file. This has been changed; a DAG's dataset schedule can now only be satisfied by events that occur when the DAG is active. While this is a breaking change, the previous behavior is considered a bug.

The behavior of time-based scheduling is unchanged, including the timetable part of DatasetOrTimeSchedule.

try_number is no longer incremented during task execution (#39336) """"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""

Previously, the try number (try_number) was incremented at the beginning of task execution on the worker. This was problematic for many reasons. For one it meant that the try number was incremented when it was not supposed to, namely when resuming from reschedule or deferral. And it also resulted in the try number being "wrong" when the task had not yet started. The workarounds for these two issues caused a lot of confusion.

Now, instead, the try number for a task run is determined at the time the task is scheduled, and does not change in flight, and it is never decremented. So after the task runs, the observed try number remains the same as it was when the task was running; only when there is a "new try" will the try number be incremented again.

... (truncated)

Commits

• 8541731 Lower down universal-pathlib minimum to 0.2.2 (#41939) (#41943)
• 3304c2a Protect against None components of universal pathlib xcom backend (#41921) (#...
• 3273171 Update RELEASE_NOTES.rst
• 4cd17c0 Update version to 2.10.1.
• 6d8e88c Add backcompat check for executors that don't inherit BaseExecutor (#41906) (...
• d177978 Upgrade UV to 0.4.1 (#41925) (#41926)
• d4c2dd0 Update release command for Airflow 2 (#41907)
• aafad2a Make Scarf usage reporting in major+minor versions and counters in buckets (#...
• fa03a32 Skip test_scan_stale_dags_when_dag_folder_change in DB isolation mode (#41893...
• 09ec261 Adding tojson filter to example_inlet_event_extra example dag (#41873) (#41890)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/aws-samples/mwaa-disaster-recovery/network/alerts).

[github-actions[bot]]

Coverage report

This PR does not seem to contain any modification to coverable code.

[dependabot[bot]]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.