o-nikolas commented on code in PR #66491:
URL: https://github.com/apache/airflow/pull/66491#discussion_r3236644274
##########
providers/git/pyproject.toml:
##########
@@ -60,7 +60,7 @@ requires-python = ">=3.10"
# After you modify the dependencies, and rebuild your Breeze CI image with
``breeze ci-image build``
dependencies = [
"apache-airflow>=3.0.0",
- "apache-airflow-providers-common-compat>=1.12.0",
+ "apache-airflow-providers-common-compat>=1.12.0", # use next version
Review Comment:
It is used when changes are made to some core functionality and used
immediately by a provider in the same PR. @potiuk wanted the Git Bundle updated
and once I did that, this was required. The below is from an agent:
```
The # use next version comment is a release coordination mechanism for
cross-provider dependencies in
the Airflow monorepo.
Problem it solves: When you add a new feature to one provider (e.g.,
common-compat) and simultaneously
use that feature in another provider (e.g., google) within the same PR,
you can't know the exact version
number that common-compat will be released as — that's determined later by
the Release Manager.
How it works:
1. You add the comment to the dependency line in pyproject.toml:
"apache-airflow-providers-common-compat>=1.14.2", # use next version
2. You do not manually bump the version — you leave it at whatever it
currently is.
3. When the Release Manager prepares the release, automation scans for #
use next version comments and
updates those version pins to the actual next version being released
(e.g., >=1.15.0), ensuring both
packages are released together with correct dependency bounds.
Tooling enforcements:
- CI checks (selective_checks.py) verify that when common-compat is
modified, other providers that
depend on the new changes have the # use next version comment
- Regular PRs are blocked from manually changing cross-dependency versions
(that's the Release Manager's
job)
- breeze release-management update-use-next-version-providers automates
the version bump at release time
It's primarily used for common-compat dependencies since that package
changes frequently and other
providers often need those changes simultaneously.
```
--
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]
