Git provider should require common-compat >=1.12.0

[ephraimbuddy]

Using git provider 0.2.1 with common.compat <1.12 causes issues in dag callbacks

[Prab-27]

Could we update this as - apache-airflow-providers-common-compat>=1.12.0 like teradata and exasol

[eladkal]

I think we have a bug with the # use next version
The test should not fail for this PR

[ephraimbuddy]

I think we have a bug with the # use next version The test should not fail for this PR

I remember being told by @jscheffl that the update should only be done by release manager. That was why I used the # use next version

[eladkal]

I think we have a bug with the # use next version The test should not fail for this PR

I remember being told by @jscheffl that the update should only be done by release manager. That was why I used the # use next version

Added label to override

[jscheffl]

I think we have a bug with the # use next version The test should not fail for this PR

I remember being told by @jscheffl that the update should only be done by release manager. That was why I used the # use next version

No, is only needed if the common.compat also is pending release (because something changed there) so that a marker is there that common-compat has increased version, the dependency is bumped accordingly.

If you are referring to featutes already released in 1.12.0 then it is good.

[eladkal]

If you are referring to featutes already released in 1.12.0 then it is good.

ideally yes but something is still broken with the scripts as the test is failing. I am not sure if I will have time to look into this in the up coming days

[Prab-27]

Does this fine to update the failing docs checks - here since it's just require dependency docs and get all green to merge this

[eladkal]

ah yeah
@ephraimbuddy you need to run pre-commits on this PR so index.rst will be updated

[amoghrajesh]

Nice thanks