One thing more I realized - I think we need to add a CHANGELOG entry - that will eventually will land in a single "1.0" changelog for "standard" provider. Cc: @eladkal -> we need to find out a way to tell our users - surely, you can use the "standar" operators from here - but here is the list of things that changed in it since the "built-in" ones.

Yes, actually discussed the same with @eladkal in #44542 - just someone need to tell me "how to make it right"

Yes, actually discussed the same with @eladkal in #44542 - just someone need to tell me "how to make it right"

Just add messages to CHANGELOG.rst for the provider ? - we can then combine all the changelog entries for 0.* versions when we release 1.0. Does it sound good as "making things right" @eladkal @jscheffl :D ?

I don't think it's right to wait for 1.0
The 0.0.x provider still goes into constraints file. We need the change log to explain users how to migrate

I don't think it's right to wait for 1.0 The 0.0.x provider still goes into constraints file. We need the change log to explain users how to migrate

Correct. What I proposed, was to continue adding it (as usual) and release in 0.n - but then when we release 1.0 with the target of being ready for "prime time" we could consolidate it manually and make a single "what's changed vs. built-in operators" release notes (and remove all the 0.* ones from 1.0 changelog). That sounds like an easy way to communicate to users - who will be looking at the changelog while migrating to Airflow 3, putting it all in 1.0 changelog will just give them all information in one place.

relates to #44559