Skip to content

Add PAC release automation - #1373

Open
rajnish-jais wants to merge 1 commit into
tektoncd:mainfrom
rajnish-jais:pac-automate-releases
Open

Add PAC release automation#1373
rajnish-jais wants to merge 1 commit into
tektoncd:mainfrom
rajnish-jais:pac-automate-releases

Conversation

@rajnish-jais

Copy link
Copy Markdown

Summary

Adds .tekton/release.yaml and .tekton/release-patch.yaml to automate releases using Pipelines-as-Code, following the exact pattern already merged in:

The .tekton/release.yaml PipelineRun fires once when a release-v* branch is first created (CEL guard: body.created == true). The .tekton/release-patch.yaml is triggered via PAC incoming webhooks for patch releases, receiving version and release_as_latest as payload params.

The companion plumbing PR to add the Repository CR in tektoncd/plumbing will follow.

Closes #1372

@tekton-robot
tekton-robot requested review from divyansh42 and khrm July 6, 2026 14:06
@tekton-robot tekton-robot added do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Jul 6, 2026
@anithapriyanatarajan

Copy link
Copy Markdown
Contributor

/release-note-none

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 16, 2026
@anithapriyanatarajan

Copy link
Copy Markdown
Contributor

@khrm @enarha @infernus01 - could you help verifying this

@rajnish-cloudbees

Copy link
Copy Markdown

@infernus01 The same fixes applied to the triggers PR are already present here:

  • windows/amd64 included in publishPlatforms in both release.yaml and release-patch.yaml
  • .github/workflows/patch-release.yaml added with PAC_REPOSITORY_NAME: tektoncd-results

rajnish-jais added a commit to rajnish-jais/plumbing that referenced this pull request Jul 20, 2026
Adds releases-triggers and releases-results namespaces with Repository
CRs so PAC can dispatch release PipelineRuns for:

- tektoncd/triggers (see tektoncd/triggers#2062)
- tektoncd/results (see tektoncd/results#1373)

Follows the same pattern as the existing chains, pipeline, pruner,
operator, and cli CRs.
rajnish-jais added a commit to rajnish-jais/plumbing that referenced this pull request Jul 20, 2026
Adds releases-triggers and releases-results namespaces with Repository
CRs so PAC can dispatch release PipelineRuns for:

- tektoncd/triggers (see tektoncd/triggers#2062)
- tektoncd/results (see tektoncd/results#1373)

Follows the same pattern as the existing chains, pipeline, pruner,
operator, and cli CRs.
@rajnish-jais
rajnish-jais force-pushed the pac-automate-releases branch from 66242bd to 29a5fc5 Compare July 21, 2026 07:14

@vdemeester vdemeester left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

steps:
- name: Trigger PAC incoming webhook
env:
PAC_INCOMING_SECRET: ${{ secrets.PAC_INCOMING_SECRET }}

- name: Trigger PAC incoming webhook
env:
PAC_INCOMING_SECRET: ${{ secrets.PAC_INCOMING_SECRET }}
@tekton-robot
tekton-robot requested a review from enarha August 18, 2026 09:40
@tekton-robot

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. release-note-none Denotes a PR that doesnt merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: automate releases with Pipelines-as-Code

6 participants