This is an automated email from the ASF dual-hosted git repository.
potiuk 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 270eb13e4a7 Add triggering PR and Push workflows for provider branches
(#45159)
270eb13e4a7 is described below
commit 270eb13e4a7fa44d9e5077dd124c0a7d154ae496
Author: Jarek Potiuk <[email protected]>
AuthorDate: Sun Dec 22 20:02:32 2024 +0100
Add triggering PR and Push workflows for provider branches (#45159)
With FAB 1.5.2 we have the first case where we need to build and
release providers for old MAJOR version. That requires `pull_request`
and `push` workflows to start when they are targetted against
`providers-*/v[VERSION]` branches.
The .asf.yaml is updated to make providers-fab/v1-5 protected and
documentation of provider's lifecycle is updated to explain how
we work with releasing past versions of providers.
---
.asf.yaml | 5 +++++
.github/workflows/ci.yml | 4 ++--
.../src/airflow/providers/MANAGING_PROVIDERS_LIFECYCLE.rst | 12 ++++++++++++
3 files changed, 19 insertions(+), 2 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 8134fddbcd9..d04efc51a26 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -118,6 +118,11 @@ github:
required_approving_review_count: 1
required_linear_history: true
required_conversation_resolution: true
+ providers-fab/v1-5:
+ required_pull_request_reviews:
+ required_approving_review_count: 1
+ required_linear_history: true
+ required_conversation_resolution: true
collaborators:
# Max 10 collaborators allowed
#
https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#assigning-the-github-triage-role-to-external-collaborators
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 80af9d54818..7971a9162ac 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -21,9 +21,9 @@ on: # yamllint disable-line rule:truthy
schedule:
- cron: '28 1,7,13,19 * * *'
push:
- branches: ['v[0-9]+-[0-9]+-test']
+ branches: ['v[0-9]+-[0-9]+-test', 'providers-*/v[0-9]+-[0-9]+]']
pull_request:
- branches: ['main', 'v[0-9]+-[0-9]+-test', 'v[0-9]+-[0-9]+-stable']
+ branches: ['main', 'v[0-9]+-[0-9]+-test', 'v[0-9]+-[0-9]+-stable',
'providers-*/v[0-9]+-[0-9]+']
workflow_dispatch:
permissions:
# All other permissions are set to none
diff --git a/providers/src/airflow/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
b/providers/src/airflow/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
index b5f918149eb..0e4a49f304e 100644
--- a/providers/src/airflow/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
+++ b/providers/src/airflow/providers/MANAGING_PROVIDERS_LIFECYCLE.rst
@@ -471,6 +471,18 @@ considered by the release management commands.
As soon as the provider is released, you should update the provider to
``state: ready``.
+Releasing providers for past releases
+=====================================
+
+Sometimes we might want to release provider for previous MAJOR when new
release is already
+released (or bumped in main). This is done by releasing them from
``providers-<PROVIDER>/vX-Y`` branch
+- for example ``providers-fab/v1-5`` can be used to release the ``1.5.2`` when
``2.0.0`` is already being
+released or voted on.
+
+The release process looks like usual, the only difference is that the specific
branch is used to release
+the provider and update all documentation, the changes and cherry-picking
should be targeting that
+branch.
+
Suspending providers
====================
