potiuk commented on issue #53829:
URL: https://github.com/apache/airflow/issues/53829#issuecomment-3132058673

   We are going to release a new version of FAB provider and airflow 2.11.1 
(which will workaround other dependency securiuty issues as well) as soon as 
https://github.com/spec-first/connexion/pull/2060 is merged and Connexion 2.15 
gets released. We are not going to release a new version of the Fab provider 
and 2.11.1 . So please comment on the 
https://github.com/spec-first/connexion/pull/2060 issue and convince Connexion 
maintainers that more people are waiting for the update to come.
   
   The best way is maybe even support (via github sponsors or other ways the 
maintainers of Connexion). The software we and them release comes without any 
guarantees (see the licence) so we do not "need to update" - we **might** (and 
connexion maintainers **might**) decide to update the version. This is not 
mandatory - even under CRA regime in EU in a year from now - you (commercial 
users) will be obliged to update to latest non-vulnerable version, and we (open 
source stewards can simply give the opportunity for you to do so).
   
   Speaking of which - you can also upgrade to Airflow 3 where FAB provider 
2.3.0 already supports Fab 4.6.3.
   
   
   Closing it as this is not an airflow issue - it's really a qyestion of 
Connexion. You might want to open an issue to Connextion and possibly - as 
suggested above your company might consider supporting their work - they are - 
as we - volunteers who releae our software for companies like you for free and 
clearly state that there are no guarantees, so it would make sense that when 
companies have excessive demands, they might also consider contributing back 
for the hard work of maintainers.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to