Skip to content

Sync v3-2-stable with v3-2-test to release 3.2.1rc3#65533

Open
vatsrahul1001 wants to merge 4 commits intov3-2-stablefrom
changes-3.2.1rc3
Open

Sync v3-2-stable with v3-2-test to release 3.2.1rc3#65533
vatsrahul1001 wants to merge 4 commits intov3-2-stablefrom
changes-3.2.1rc3

Conversation

@vatsrahul1001
Copy link
Copy Markdown
Contributor

Time for 3.2.1rc3!

  • Read the Pull Request Guidelines for more information. Note: commit author/co-author name and email in commits become permanently public when merged.
  • For fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
  • When adding dependency, check compliance with the ASF 3rd Party License Policy.
  • For significant user-facing changes create newsfragment: {pr_number}.significant.rst, in airflow-core/newsfragments. You can add this file in a follow-up commit after the PR is created so you know the PR number.

github-actions bot and others added 4 commits April 20, 2026 16:28
Lack of it might make `uv` to make bad choices when resolving
dependencies. For example this happened in

dde322c#diff-f5c8f9fc9a8fd6114a3f388511416a71c5c2accc6d04e89c3e358d9085f768db

By limiting FAB we avoid downgrading Fab provider to some old
versions that were technically not limited but not working in
Python 3.13 and 3.14
(cherry picked from commit b31376e)

Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
) (#65527)

Update constraints on stable branches (v*-stable) on every push, not
only when uv.lock changes. Constraints on stable branches reflect the
last successful CI run for the released line, so they should be
refreshed whenever any change lands — not gated on uv.lock churn.

The main/v*-test workflow keeps the uv.lock path filter, since those
branches still regenerate constraints only when dependencies actually
change.
(cherry picked from commit 0c88719)
… run (#65518) (#65522)

(cherry picked from commit 820e9d2)

Co-authored-by: Rahul Vats <43964496+vatsrahul1001@users.noreply.github.com>
@vatsrahul1001 vatsrahul1001 requested a review from jscheffl April 20, 2026 11:42
Copy link
Copy Markdown
Contributor

@ephraimbuddy ephraimbuddy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the release_note be updated e.g the release date?

@vatsrahul1001
Copy link
Copy Markdown
Contributor Author

Should the release_note be updated e.g the release date?

I am planning to do Accelerated vote for rc3 as we have spent good testing time for rc1 and rc2. Release date is already updated to 21 April here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants