Add PAC release automation#2062
Conversation
Adds .tekton/release.yaml and .tekton/release-patch.yaml to automate releases using Pipelines-as-Code, following the pattern already merged in tektoncd/chains and tektoncd/pipeline. Closes tektoncd#2061
|
@rajnish-jais: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
tekton-robot
added
do-not-merge/release-note-label-needed
2 participants
Summary
Adds
.tekton/release.yamland.tekton/release-patch.yamlto automate releases using Pipelines-as-Code, following the exact pattern already merged in:The
.tekton/release.yamlPipelineRun fires once when arelease-v*branch is first created (CEL guard:body.created == true). The.tekton/release-patch.yamlis triggered via PAC incoming webhooks for patch releases, receivingversionandrelease_as_latestas payload params.The companion plumbing PR to add the
RepositoryCR in tektoncd/plumbing will follow.Closes #2061