This is an automated email from the ASF dual-hosted git repository.
rahulvats pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new bbec651e845 Doc: Add test-to-stable PR example with allow provider
dependency bump label (#65341)
bbec651e845 is described below
commit bbec651e845c729053b9aac796dd6eaa12e100ac
Author: Jarek Potiuk <[email protected]>
AuthorDate: Thu Apr 16 06:15:16 2026 +0200
Doc: Add test-to-stable PR example with allow provider dependency bump
label (#65341)
---
dev/README_RELEASE_AIRFLOW.md | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/dev/README_RELEASE_AIRFLOW.md b/dev/README_RELEASE_AIRFLOW.md
index 0230ece5f21..37688d85aa8 100644
--- a/dev/README_RELEASE_AIRFLOW.md
+++ b/dev/README_RELEASE_AIRFLOW.md
@@ -501,6 +501,23 @@ uv tool install -e ./dev/breeze
- PR from the 'test' branch to the 'stable' branch
+ Cherry-picked commits often include provider dependency bumps (changes to
`>=` constraints on
+ `apache-airflow-providers-*` packages in `pyproject.toml`). CI blocks such
changes by default —
+ only Release Managers should perform them. To allow the PR to pass, add the
+ `allow provider dependency bump` label (and `skip common compat check` if
common.compat files
+ changed). For example:
+
+ ```shell script
+ gh pr create \
+ --base v3-2-stable \
+ --head v3-2-test \
+ --title "Airflow ${VERSION}: test to stable" \
+ --label "allow provider dependency bump" \
+ --label "skip common compat check" \
+ --body "Sync v3-2-test into v3-2-stable for Airflow ${VERSION} release." \
+ --web
+ ```
+
> [!TIP]
> **Shortcut for first RC candidates:** When preparing the first RC candidate
> for a new minor release
> (e.g., 3.2.0rc1), it is unlikely to be approved on the first attempt — bugs
> are typically found during
