ephraimbuddy commented on issue #30427: URL: https://github.com/apache/airflow/issues/30427#issuecomment-1494303703
> > #30216 should not be included in a release yet. Is there a way this can be avoided @eladkal > > Good catch, but I think this is a wrong question. > > Part of the change is in `cncf.kubernetes` @ephraimbuddy -> this is what''s being released, so if it is not compatible with currently released airflow, it should be fixed. Generally the expectation is that if there is any change in a provider that require some changes to airflow core, one of the two things happen: > > a) it is made in a backwards-compatble way that will be well handled in the older airflow version (by fallback, etc.) b) it limits min-airflow version to be the future airflow version in `provider.yaml` > > In this case, I think a) case is the right approach, so my question is (and mostly to you @ephraimbuddy :) > > Is it backwards compatible with airlfow 2.3+? > > if yes-> all is cool and we can release `cncnf.kubernetes` as is. If not, we should remove `cncf.kubernetes` from the release and fix it so that it is backwards compatible (and prepare rc2). Yeah. It’s backwards compatible. I discussed with @eladkal and he said the release doesn’t include the test files and it’s only in the test files that we made import that should have caused backwards incompatibility. -- 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]
