jscheffl opened a new issue, #61313:
URL: https://github.com/apache/airflow/issues/61313

   ### Apache Airflow version
   
   Other Airflow 3 version (please specify below)
   
   ### If "Other Airflow 3 version" selected, which one?
   
   3.1.7rc1
   
   ### What happened?
   
   While checking release candidate of Airflow 3.1.7rc1 I noticed that 
EdgeExecutor UI plugin fails validating version check. This is probably due to 
#61078 which added a version check in UI
   
   Opening plugin UI fails in UI with error:
   
   <img width="349" height="281" alt="Image" 
src="https://github.com/user-attachments/assets/9ae2c910-e207-4fcb-8cc8-d049c54bc986";
 />
   
   Console shows:
   
   <img width="1226" height="384" alt="Image" 
src="https://github.com/user-attachments/assets/6005705b-2781-46b3-bc82-d934e32493e6";
 />
   
   ### What you think should happen instead?
   
   No error. Should just work
   
   ### How to reproduce
   
   Checkout latest main in a dev env. (1) build edge provider via `breeze 
release-management prepare-provider-distributions edge3 common.compat 
--skip-tag-check` and then start Airflow 3.1.7rc1 via `breeze start-airflow 
--load-example-dags --executor EdgeExecutor --use-airflow-version 
3.1.7rc1--use-distributions-from-dist`
   
   ### Operating System
   
   Ubuntu 24.04
   
   ### Versions of Apache Airflow Providers
   
   Edge Executor from latest main. But most probably the same with 3.0.1
   
   ### Deployment
   
   Other
   
   ### Deployment details
   
   breeze as ^^
   
   ### Anything else?
   
   When patching version number manually down to be 3.1.7 (without RC1) then it 
is working fine.
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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