Skip to content

Commit 4199e4e

Browse files
github-actions[bot]dependabot[bot]potiukjustinpakzad
authored
[v3-2-test] Doc: Add test-to-stable PR example with allow provider dependency bump label (#65341) (#65352)
* [v3-2-test] Bump actions/github-script in the github-actions-updates group (#65150) (#65160) Bumps the github-actions-updates group with 1 update: [actions/github-script](https://github.com/actions/github-script). Updates `actions/github-script` from 8.0.0 to 9.0.0 - [Release notes](https://github.com/actions/github-script/releases) - [Commits](actions/github-script@ed59741...3a2844b) (cherry picked from commit e5a047c) --- updated-dependencies: - dependency-name: actions/github-script dependency-version: 9.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: github-actions-updates ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * [v3-2-test] Added breeze generate issue content for airflow-ctl (#65042) (#65241) * Add breeze generate issue content for airflow-ctl * add new command to doc (cherry picked from commit b24538b) Co-authored-by: Justin Pakzad <114518232+justinpakzad@users.noreply.github.com> * [v3-2-test] Run release calendar verification on its own schedule (#65118) (#65242) * Move release calendar verification to its own scheduled workflow Run dev/verify_release_calendar.py from a dedicated daily scheduled workflow instead of as a canary job in the main CI pipeline, and notify the #release-management Slack channel when the check fails so the issue is surfaced to release managers directly. * Include wiki and calendar links in release calendar Slack alert (cherry picked from commit 048e9a1) * [v3-2-test] Doc: Add test-to-stable PR example with allow provider dependency bump label (#65341) (cherry picked from commit bbec651) Co-authored-by: Jarek Potiuk <jarek@potiuk.com> --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Jarek Potiuk <jarek@potiuk.com> Co-authored-by: Justin Pakzad <114518232+justinpakzad@users.noreply.github.com>
1 parent e6accdd commit 4199e4e

1 file changed

Lines changed: 17 additions & 0 deletions

File tree

dev/README_RELEASE_AIRFLOW.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -503,6 +503,23 @@ uv tool install -e ./dev/breeze
503503

504504
- PR from the 'test' branch to the 'stable' branch
505505

506+
Cherry-picked commits often include provider dependency bumps (changes to `>=` constraints on
507+
`apache-airflow-providers-*` packages in `pyproject.toml`). CI blocks such changes by default —
508+
only Release Managers should perform them. To allow the PR to pass, add the
509+
`allow provider dependency bump` label (and `skip common compat check` if common.compat files
510+
changed). For example:
511+
512+
```shell script
513+
gh pr create \
514+
--base v3-2-stable \
515+
--head v3-2-test \
516+
--title "Airflow ${VERSION}: test to stable" \
517+
--label "allow provider dependency bump" \
518+
--label "skip common compat check" \
519+
--body "Sync v3-2-test into v3-2-stable for Airflow ${VERSION} release." \
520+
--web
521+
```
522+
506523
> [!TIP]
507524
> **Shortcut for first RC candidates:** When preparing the first RC candidate for a new minor release
508525
> (e.g., 3.2.0rc1), it is unlikely to be approved on the first attempt — bugs are typically found during

0 commit comments

Comments
 (0)