Skip to content
Discussion options

You must be logged in to vote

Correct - as mentioned in cern-sis/issues-inspire#1084 (comment) and as you can see in the PR, this change is not back-ported to 3.1 (it's just to big and too risky to backport) - it will be fixed in 3.2.

You can follow the Release Plan and subscribe to devlist or attend our regular dev calls See Airflow 3.x to keep yourself updated on when it will be ready for alpha/beta/rc testing and participate in those tests.

Of course if you really want to have it in 3.1 - you can propose a PR back-porting the change, making sure it's green and convincing maintainers that it is safe-enough to backport it - for example building a test package containing the fix and trying it in your case and providin…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@potiuk
Comment options

potiuk Jan 15, 2026
Collaborator

Answer selected by MaluNoPeleke
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants