Story (Required)

Any relevant RN from upstream needs to be added to the release notes section in a consolidated manner and docs team will be referring to this instead of google docs moving forward.

Background (Required)

<Describes the context or background related to this story>

Out of scope

• Drafting the release notes text.

• Review and approval of release notes.

• Publication of the release notes.

Approach (Required)

• Fetch the list of PRs/issues merged upstream for v1.20 from GitHub (tektoncd/hub repo).

• Identify PRs relevant to OpenShift Pipelines (skip upstream-only changes not consumed downstream, if applicable).

• Organize contributions into categories (features, enhancements, bug fixes).

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

RN section is added with a consolidated list of revelant upstream release notes.

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met