Add triggering PR and Push workflows for provider branches #45159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
cc: @shubhamraj-git |
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.
potiuk
force-pushed
the
add-pull-request-and-push-triggering-for-providers-backport
branch
from
5662089 to
7147e52
Compare
jscheffl
approved these changes
Dec 22, 2024
It's actually very straightforward :). And I am glad we can finally try it. |
gopidesupavan
approved these changes
Dec 22, 2024
potiuk
deleted the
add-pull-request-and-push-triggering-for-providers-backport
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With FAB 1.5.2 we have the first case where we need to build and release providers for old version. That requires
pull_requestandpushworkflows to start when they are targetted againstproviders-*/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.
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.