Lee-W commented on issue #54714: URL: https://github.com/apache/airflow/issues/54714#issuecomment-3744423224
> > [@sjyangkevin](https://github.com/sjyangkevin) Another thing I'm thinking of is using task-sdk version instead of the airflow version 🤔 Our message might need to be adjusted a bit, but it would be more accurate. WDYT? > > [@Lee-W](https://github.com/Lee-W) , thanks for the feedback. I think it makes sense. I am trying to think of eventually what types of changes we should include in the code. If we would like to use it to cover everything that is removed/moved from airflow 3.1; I think we can have a new replacement enum and use that to outline the sdk version. e.g. moved from Airflow 3.1 to task-sdk 1.x.x. > > I think keep the Airflow version and use it to separate the code might still be better as users may selectively use the rules based on the their airflow version > > Let me know if it sounds make sense to you, and feel free to correct me if I understand it wrong. Thanks!! What's in my mind is something like (`A has been moved to B since airflow 3.1 (with task-sdk 1.1)`) WDYT? -- 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]
