Sync v3-1-stable with v3-1-test to release 3.1.7rc1 #61160
Merged
+5,250
−2,335
Conversation
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
…60252) The docstring previously indicated the Airflow 2 behavior of allowing both key and task_ids to be set to None to query all values. These have been updated to indicate that key cannot be None and that task_ids will default to the current task_id. (cherry picked from commit b8effe9) Co-authored-by: GlenboLake <glenbolake@gmail.com> Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
* Add virtualization to grid view * Remove all jsx inline function declarations * Remove awkward Bar code reuse, add nav mode const * Remove extraneous code * Update airflow-core/src/airflow/ui/src/layouts/Details/Grid/TaskNames.tsx * Fix scrollbars and horizontal scrolling --------- (cherry picked from commit 7a64304) Co-authored-by: Brent Bovenzi <brent@astronomer.io> Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com>
…2 in breeze (#60264) (#60267) When installing Airflow 2 in Breeze, we need to add pydantic as extra, because pydantic in Airflow 2 was not a required dependency and installation of airflow even with constraints willl not downgrade pydantic to the version that was supported in Airflow 2. When we detect that airflow 2 is installed (either by specified version number or by retrieving the version from the dist package) we simply extend the extras with pydantic and that causes airflow installation to downgrade pydantic to the version that is specified in constraints of selected airflow version. (cherry picked from commit 336b816) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…airflow (#60304) (#60305) When Airflow is installed in breeze with `--use-airflow-version` and it's either wheel, dist or version number, we should use PyPI constraints, rather than source constraints, because in some edge cases, pre-installed providers might be installed using different version than the version specified in PyPI constraints. This might happen if the dependency resolution run by uv will determine that another package is more important to be installed in higher version and that higher version conflicts with newer preinstalled provider version. In this case Fab Provider is pinned with fab provider and the version of fab provider in v3-1-test sources was pretty old. (cherry picked from commit e0c5458) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
…60158) (#60332) * Add description about Gen-AI contributions to our guide * Update contributing-docs/05_pull_requests.rst * fixup! Update contributing-docs/05_pull_requests.rst * Update contributing-docs/05_pull_requests.rst --------- (cherry picked from commit 7d7908d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Co-authored-by: Pierre Jeambrun <pierrejbrun@gmail.com> Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
* CI: Upgrade important CI environment * Fix action pinning
…60368) (#60381) * Add Linux favour of installing dependencies for release * Add Linux favour of installing dependencies for release for providers * Convert instructions to one liner --------- (cherry picked from commit 67c95c3) Co-authored-by: Bugra Ozturk <bugraoz93@users.noreply.github.com> Co-authored-by: Jens Scheffler <95105677+jscheffl@users.noreply.github.com>
jscheffl
approved these changes
Jan 28, 2026
Contributor
jscheffl
left a comment
jscheffl
left a comment
There was a problem hiding this comment.
Wow, this is hug again!
Skimmed over changes bus as of large change set only spot checks.
Still am a bit worried about the plugin problems I am discussing in parallel with Pirerre.
* fix(ui): avoid chart annotation left error by removing resizeDelay * fix(ui): keep resizeDelay and set annotation clip false in gantt * fix(ui): adjust annotation clip false position per prek formatting (cherry picked from commit 122146f)
Import error stopped showing on UI after #60801 which removed the early bypass for users with access to all DAGs. When a DAG file has an import error, the DAG doesn't exist in DagModel (because it failed to import). The inner join with DagModel filters out these import errors because there's no matching row. This was always broken for users without "read all" permissions but was masked by the early return path.
ephraimbuddy
force-pushed
the
changes-3.1.7rc1
branch
from
d724c61 to
d10388e
Compare
ephraimbuddy
requested review from
Fokko,
josh-fell and
o-nikolas
as code owners
amoghrajesh
approved these changes
Jan 30, 2026
Contributor
amoghrajesh
left a comment
amoghrajesh
left a comment
There was a problem hiding this comment.
Oh my, thats a big diff, likely due to NOTICE updates. Some nits, otherwise LGTM
…60734) (#61230) * dag_processing: initialize versioned bundles for callbacks (#52040) * Apply suggestion from @amoghrajesh * Apply suggestion from @amoghrajesh * Apply suggestion from @amoghrajesh * Add unit tests for callback handling and improve logging in Dag processing * fix CI static checks #2 --------- (cherry picked from commit cac9c0b) Co-authored-by: Aaron Chen <nailo2c@gmail.com> Co-authored-by: Amogh Desai <amoghrajesh1999@gmail.com>
ephraimbuddy
force-pushed
the
changes-3.1.7rc1
branch
from
d10388e to
78e5b16
Compare
Lee-W
reviewed
Jan 30, 2026
…61232) (#61243) When the DAG processor resorts its file queue by modification time (e.g., after a bundle refresh), files with pending callbacks could lose their position at the front of the queue. This could delay callback execution (like DAG failure callbacks) if those files happened to have older modification times. The fix partitions the queue during resort: callback files stay at the front in their original order, while only regular files are sorted by mtime. (cherry picked from commit f5e70fc) Co-authored-by: Jed Cunningham <66968678+jedcunningham@users.noreply.github.com>
ephraimbuddy
force-pushed
the
changes-3.1.7rc1
branch
2 times, most recently
from
628dfdf to
dfdff53
Compare
ephraimbuddy
force-pushed
the
changes-3.1.7rc1
branch
from
dfdff53 to
d82bb10
Compare
vatsrahul1001
approved these changes
Jan 30, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
20 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.
Time for 3.1.7rc1
Release Note: - Update RELEASE_NOTES.rst
Version Update: - Update Airflow Version to 3.1.7