Skip to content

Status of testing of Apache Airflow 3.2.1rc3 #65336

Closed

Description

@vatsrahul1001

Body

We are kindly requesting that contributors to Apache Airflow RC 3.2.1rc1 help test the RC.

Please let us know by commenting if the issue is addressed in the latest RC.

Thanks to all who contributed to the release (probably not a complete list!):
@andreahlert @YoannAbriel @dandanseo123 @dabla @jscheffl @tysoncung @MichaelRBlack @amordoch @sjyangkevin @henry3260 @nagasrisai @bennyc0de @Petrinax @justinpakzad @Subham-KRLX @Lee-W @kaxil @bugraoz93 @holmuk @uranusjr @pierrejeambrun @Mayankaggarwal8055 @tuzonghua @shubhamraj-git @amoghrajesh @leossantos @ephraimbuddy @avolant @potiuk @antonio-mello-ai @gopidesupavan @darkag @fat-catTW @ashb @vatsrahul1001 @wolfdn @rjgoyln @alamashir @cmarteepants @steveahnahn @kacpermuda @wjddn279 @yavin87 @Owen-CH-Leung @vagetablechicken

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Activity

  1. bugraoz93 commented on Apr 16, 2026

    @bugraoz93
    Contributor

    My changes look good! They relate to airflow-ctl as well, seeing some. I will double-check the breeze commands and will amend this to exclude airflow-ctl labelled PRs from issue generation and similar automations.
    We have a label to exclude, but if we programmatically exclude all ctl-related work, that will be easier to maintain

  2. Subham-KRLX commented on Apr 16, 2026

    @Subham-KRLX
    Contributor

    Tested the link target detection for extra_links (#64967) on the latest RC I have verified that the logic correctly assigns target="_self" for internal paths and target="_blank" for external URLs. Unit tests covering these scenarios are also passing locally.

  3. Owen-CH-Leung commented on Apr 17, 2026

    @Owen-CH-Leung
    Contributor

    I can confirm that the opensearch provider is working with airflow 3.2.1. Thanks

  4. changed the title [-]Status of testing of Apache Airflow 3.2.1rc1[/-] [+]Status of testing of Apache Airflow 3.2.1rc2[/+] on Apr 17, 2026
  5. leossantos commented on Apr 19, 2026

    @leossantos
    Contributor

    I tested the fix in Asset Scheduling using Breeze. This same fix is already running in production at the company I work for.

    #64738

  6. henry3260 commented on Apr 19, 2026

    @henry3260
    Member

    Test #64416 looks great; it only relates to changing the exit code.

  7. potiuk commented on Apr 20, 2026

    @potiuk
    Member

    Checked all my changes ! looks good.

  8. wjddn279 commented on Apr 20, 2026

    @wjddn279
    Contributor

    I confirm my change is applied well but I found the issue in apache/airflow:3.1.2rc2image installed provider-fabversion doesn't support python 3.13
    https://apache-airflow.slack.com/archives/C03G9H97MM2/p1776659748627579

  9. justinpakzad commented on Apr 20, 2026

    @justinpakzad
    Contributor

    My changes are all good!

  10. Lee-W commented on Apr 20, 2026

    @Lee-W
    Member

    not directly related to airflow-core, but fab provider has an issue that blocks users from upgrading airflow 3.2.0 to 3.2.1 if they're using fab. fix is the one below

    #65540

  11. bennyc0de commented on Apr 20, 2026

    @bennyc0de
    Contributor

    UI changes looking good from my fix #64640

  12. bugraoz93 commented on Apr 20, 2026

    @bugraoz93
    Contributor

    This RC voting has been canceled. Will be RC3. Thanks all!

  13. bugraoz93 commented on Apr 20, 2026

    @bugraoz93
    Contributor
  14. jscheffl commented on Apr 20, 2026

    @jscheffl
    Contributor

    @bugraoz93 the issue usually stays open for all RCs and the title is updated.

  15. bugraoz93 commented on Apr 20, 2026

    @bugraoz93
    Contributor

    @bugraoz93 the issue usually stays open for all RCs and the title is updated.

    Oops my bad! Make sense! Good to know, thanks Jens! I created a couple different for ctl release last time. Will follow this approach there too which is a lot easier for sure

    Sorry for confusion all! I was trying to help 😅

  16. vatsrahul1001 commented on Apr 20, 2026

    @vatsrahul1001
    ContributorAuthor

    @bugraoz93 the issue usually stays open for all RCs and the title is updated.

    Oops my bad! Make sense! Good to know, thanks Jens! I created a couple different for ctl release last time. Will follow this approach there too which is a lot easier for sure

    Sorry for confusion all! I was trying to help 😅

    No worries

  17. potiuk commented on Apr 20, 2026

    @potiuk
    Member

    @bugraoz93 the issue usually stays open for all RCs and the title is updated.

    Oops my bad! Make sense! Good to know, thanks Jens! I created a couple different for ctl release last time. Will follow this approach there too which is a lot easier for sure
    Sorry for confusion all! I was trying to help 😅

    No worries

    Actually I found out that it's easier to close the issue, open the new one and then ask Claude to check the same boxes in the new one as they were in the old one.

    Worked like a charm last time.

  18. changed the title [-]Status of testing of Apache Airflow 3.2.1rc2[/-] [+]Status of testing of Apache Airflow 3.2.1rc3[/+] on Apr 21, 2026
  19. vatsrahul1001 commented on Apr 21, 2026

    @vatsrahul1001
    ContributorAuthor

    @bugraoz93 the issue usually stays open for all RCs and the title is updated.

    Oops my bad! Make sense! Good to know, thanks Jens! I created a couple different for ctl release last time. Will follow this approach there too which is a lot easier for sure
    Sorry for confusion all! I was trying to help 😅

    No worries

    Actually I found out that it's easier to close the issue, open the new one and then ask Claude to check the same boxes in the new one as they were in the old one.

    Worked like a charm last time.

    With renaming what I like is we will have all status confirmation from contributors on single issue.

  20. potiuk commented on Apr 21, 2026

    @potiuk
    Member

    @bugraoz93 the issue usually stays open for all RCs and the title is updated.

    Oops my bad! Make sense! Good to know, thanks Jens! I created a couple different for ctl release last time. Will follow this approach there too which is a lot easier for sure
    Sorry for confusion all! I was trying to help 😅

    No worries

    Actually I found out that it's easier to close the issue, open the new one and then ask Claude to check the same boxes in the new one as they were in the old one.
    Worked like a charm last time.

    With renaming what I like is we will have all status confirmation from contributors on single issue.

    Yep. But I think just linking to the old issue is also good :D

  21. tuzonghua commented on Apr 21, 2026

    @tuzonghua
    Contributor

    Confirmed #62230 is working for me

  22. cmarteepants commented on Apr 21, 2026

    @cmarteepants
    Collaborator

    Confirmed #64852 is working! Tried setting the api theme config as an empty dict, setting something for just globalCss, and then setting something for just for tokens. Also confirmed that when omitting GlobalCss, we are defaulting to Airflow's css configs, not Chakra's.

  23. potiuk commented on Apr 22, 2026

    @potiuk
    Member

    With renaming what I like is we will have all status confirmation from contributors on single issue.

    cc: @vatsrahul1001 -> see what Claude did in #65643 (comment) when I asked it :)

  24. vatsrahul1001 commented on Apr 22, 2026

    @vatsrahul1001
    ContributorAuthor

    Thanks for all testing efforts 3.2.1 released

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind:metaHigh-level information important to the community

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions