> > > Mainly for the case of standard provider and the integration > chicken-and-egg problem to un-block the work. >
Yes - for example this: https://github.com/apache/airflow/pull/42654#issuecomment-2387999058 that resulted in some conditional "skip-if" that should not be needed when we release final version of the provider - having a .dev* version of provider in PyPI which we could release semi-frequently with new code should solve the problem entirely. > For edge.. no pressure, some PRs are waiting (still unfortunately). As I > am biased for edge, I'd first propose for standard as PR #42676 > Agree. Edge will not be pre-installed and there should be no dependency on it in the airflow CI, or other providers that might cause such failures.
