GitHub user potiuk edited a comment on the discussion: Sentry fixed wasn't really merged in 3.1.4
Correct - as mentioned in https://github.com/cern-sis/issues-inspire/issues/1084#issuecomment-3714465323 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](https://cwiki.apache.org/confluence/display/AIRFLOW/Release+Plan) and subscribe to devlist or attend our regular dev calls See [Airflow 3.x](https://cwiki.apache.org/confluence/display/AIRFLOW/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 providing logs confirming the backport is working fine. Airflow has > 3500 contributors and you can eeasily become one by backporting it and leading such backport PR to completion. We have detailed guide on backporting https://github.com/apache/airflow/blob/main/dev/README_AIRFLOW3_DEV.md#how-to-backport-pr-with-github-actions (and the following chapters) and quite comprehensive contributor's guidelines https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst that you can follow (or anyone you will find who can do it if you don't feel like you can do it yourself. GitHub link: https://github.com/apache/airflow/discussions/60401#discussioncomment-15508009 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
