bugraoz93 commented on PR #57171: URL: https://github.com/apache/airflow/pull/57171#issuecomment-3445188273
> I'm unsuer as to why we need changes for airflowctl on the v3-1 branches? That's just for apache-airflow-core and apache-airflow-task-sdk releases, and airflowctl is independent of Airflow versions/releases, isn't it? Great point Ash! The need for syncing this branch to v3-1 is to trigger integration tests for v3-1 because it uses the built prod image in the test that was created in the same workflow/pipeline. This will be v1.0.0 and we have planned to provide support for v3-1 for airflowctl but ended up a bit late than the v3-1 cut. We are running CI pipelines on a schedule for main and v-3-1. To stop syncing, we need to run the integration tests for all supported versions from main to provide a fully tested airflowctl version at time T in regular development and release cycles. I will plan this and make it possible for the next release cycles. This was a lot easier for the first iteration. Maybe a bit in more future, we may even split airflowctl CI and run in different schedules using more decoupled approach -- 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]
