Sync 2-11-test to 2-11-stable with 2.11.1 release notes#61921
Open
potiuk wants to merge 59 commits intov2-11-stablefrom
Open
Sync 2-11-test to 2-11-stable with 2.11.1 release notes#61921potiuk wants to merge 59 commits intov2-11-stablefrom
potiuk wants to merge 59 commits intov2-11-stablefrom
Conversation
Bumps [packaging](https://github.com/pypa/packaging) from 24.2 to 25.0. - [Release notes](https://github.com/pypa/packaging/releases) - [Changelog](https://github.com/pypa/packaging/blob/main/CHANGELOG.rst) - [Commits](pypa/packaging@24.2...25.0) --- updated-dependencies: - dependency-name: packaging dependency-version: '25.0' dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [keyring](https://github.com/jaraco/keyring) from 10.1 to 25.6.0. - [Release notes](https://github.com/jaraco/keyring/releases) - [Changelog](https://github.com/jaraco/keyring/blob/main/NEWS.rst) - [Commits](jaraco/keyring@10.1...v25.6.0) --- updated-dependencies: - dependency-name: keyring dependency-version: 25.6.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [pluggy](https://github.com/pytest-dev/pluggy) from 1.5.0 to 1.6.0. - [Changelog](https://github.com/pytest-dev/pluggy/blob/main/CHANGELOG.rst) - [Commits](pytest-dev/pluggy@1.5.0...1.6.0) --- updated-dependencies: - dependency-name: pluggy dependency-version: 1.6.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [trove-classifiers](https://github.com/pypa/trove-classifiers) from 2025.4.28.22 to 2025.5.9.12. - [Release notes](https://github.com/pypa/trove-classifiers/releases) - [Commits](pypa/trove-classifiers@2025.4.28.22...2025.5.9.12) --- updated-dependencies: - dependency-name: trove-classifiers dependency-version: 2025.5.9.12 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [flit-core](https://github.com/pypa/flit) from 3.11.0 to 3.12.0. - [Changelog](https://github.com/pypa/flit/blob/main/doc/history.rst) - [Commits](pypa/flit@3.11.0...3.12.0) --- updated-dependencies: - dependency-name: flit-core dependency-version: 3.12.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…lth endpoint (#48612) * check if stand alone dag processor is used * Update airflow/api/common/airflow_health.py Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> * fix tests * update tests --------- Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com>
## Why `airflow db migrate` failed when I migrated an old airflow instance to 2.11.0rc1 ## What Following up #49301 and trying to fix some found issues * `0093 upgrade, 0100 upgrade, 0060 downgrade, 0064 downgrade`: since SQite does not support constant drop, follow how #49301 deals with fk for SQlite * `0110`: backport _drop_fkey_if_exists for handling fk in sqlite * `0142`: Explicitly list down the column names when recreating dag_run table * `0073`: add a safeguard to ensure we're not wrongly update the name
Bumps [hatch](https://github.com/pypa/hatch) from 1.14.0 to 1.14.1. - [Release notes](https://github.com/pypa/hatch/releases) - [Commits](pypa/hatch@hatch-v1.14.0...hatch-v1.14.1) --- updated-dependencies: - dependency-name: hatch dependency-version: 1.14.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [flit](https://github.com/pypa/flit) from 3.10.1 to 3.12.0. - [Changelog](https://github.com/pypa/flit/blob/main/doc/history.rst) - [Commits](pypa/flit@3.10.1...3.12.0) --- updated-dependencies: - dependency-name: flit dependency-version: 3.12.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ts-3.8.txt does not exist in 2.11 (#51049) * docs: replace constraints-3.8.txt as constraints-3.9.txt as constraints-3.8.txt does not exists in 2.11 * docs: remove more python 3.8 references for reducing confusion
…#51435) When we removed hatch_build.py in Airflow 3 we changed the way how we detect automatically if breeze should be reinstalled when you switch to another directory and it stopped working when you had Airflow 2 checked out (say v2-11-test) - this one brings switching back (should be backported to v2-11-test to also allow switching breeze automatically from v2-11-test branch. (cherry picked from commit b09e661)
Address inproper input element width when no options are present in a multi-select field for a DAG parameter in the DAG trigger page. If the parameter: * is in a section: the element would become too narrow making the dropdown options unreadable. * is NOT in a section: the element would overflow it's parent if re-sized smaller Address by setting width to fill the parent element as other DAG trigger paramter input fields behave. closes: #50322
…51904) Sometimes, somehow, the end of log mark can be missing, and when that happens the streaming log reader enters an infinite loop. Instead, if the task is in a non-running state and we stop receiving log lines but never get the end of log mark, we assume we won't and stop trying. We do tell emit that we are stopping though.
This test notoriously fails in CI in v2-11-test but it is never failing when running in isolation. The nature of this test is that it indeed might fail when run in limited environment with less memory or CPU or when other tests are runnig in another container. Quarantining this test will make it runs in isolated environment - it will not run in parallel to other tests and we will still be able to see if it failed (but it's failure will not prevent the whole job to fail). This test has been completely removed in Airflow 3 as we switched from connexion to fast_api so quarantining it now seems like the easiest way to get back to green zone.
Those two tests fail "quarantine" tests collection and we should remove it in 2.11 - there are no provider tests anyway
…t tables first (#51952) (#52211) * Fix archival for cascading deletes by archiving dependent tables first (#51952) Co-authored-by: Jed Cunningham <jedcunningham@apache.org> (cherry picked from commit c77fdd6) (cherry picked from commit b06d15a) * Fix test --------- Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
…-mapped @task_group's (#51668) * xcom_arg expansion fix for v2-11 * Removing previously-added file, not needed for v2-11
In #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. (cherry picked from commit 97bbf3b) Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
potiuk
requested review from
XD-DENG,
ashb,
bbovenzi,
dstandish,
ephraimbuddy,
hussein-awala,
jedcunningham,
jhtimmins,
mik-laj,
mobuchowski,
o-nikolas,
ryanahamilton and
uranusjr
as code owners
boring-cyborg
bot
added
area:dev-tools
area:production-image
Member
Author
|
Ready to review :) |
potiuk
changed the title
potiuk
changed the title
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
14 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.
Was generative AI tooling used to co-author this PR?
{pr_number}.significant.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.