Improve documentation for updating provider dependencies

[potiuk]

• mention that you should run pre-commit or breeze static-check command
• mention that you need to run uv sync or pip install
• mention that you need to rebuild breeze image

Add comment for all pyproject.toml (and regenerate all the provider build files) just before the dependencies section in all provider's pyproject toml files - to get contributors more likely to read the instructions.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[gopidesupavan]

It updated all the provides because of schema change in template file?

[potiuk]

It updated all the provides because of schema change in template file?

I manually run breeze release-management prepare-provider-documentation --reapply-templates-only --answer yes to apply them. This is doing the same as what release manager would do but without bumping version numbers and regenerating commit list and changelog entries, just applying templates and regenerating what is automaticlaly generated.

[raphaelauv]

a small question , uv sync remove the "necessary" packages to run unit test out of breeze 'directly in IDE) , is there an option to have uv sync keep the test requirements ?

thanks

[potiuk]

a small question , uv sync remove the "necessary" packages to run unit test out of breeze 'directly in IDE) , is there an option to have uv sync keep the test requirements ?

Yes --extra devel --extra devel-tests - it's explained in the contributing docs:

https://github.com/apache/airflow/blob/main/contributing-docs/07_local_virtualenv.rst#creating-virtualenvs-with-uv

And yes, it's not obvious, but as soon as I move tests-common to a real package (waited for www removal - I hope to do it today or during the weekend), we will have all the "devel" dependencies added automatically to dev dependency group, so we will no longer need those extras for uv sync.

This is one of the reasons I want to make tests-common a separate "real" distribution - because currently it's just a "package" in "airflow" and it requires the extra deps to be added.

[raphaelauv]

thanks @potiuk 👍