Skip to content

Doc: Add test-to-stable PR example with allow provider dependency bump label #65341

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
vatsrahul1001 merged 1 commit into from
Apr 16, 2026
Merged

Doc: Add test-to-stable PR example with allow provider dependency bump label #65341

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions dev/README_RELEASE_AIRFLOW.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading