Story (Required)

Today we keep updating manually the supported versions of Pipeline on each `task-*` repo

for example here https://github.com/openshift-pipelines/task-containers/blob/main/.github/workflows/test.yaml#L21-L25 

1. If we want to remove v0.44.5 from all the `task-` repo need to be updated manually and this is a tedious job instead lets update in one place which is here https://github.com/openshift-pipelines/hack which intern update all the `task-` repo

2. always try to keep pipelines version supported similar to what supported in OSP

ex: OSP 1.13, 1.14 

More info : https://redhat-internal.slack.com/archives/C050H792L2Y/p1711619831216079

Background (Required)

<Describes the context or background related to this story>

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

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

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

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