Skip to content

ci(github): add workflow to tag downstream repos post-release - #839

Open
divyansh42 wants to merge 1 commit into
mainfrom
add-tag-workflow
Open

divyansh42 wants to merge 1 commit into
mainfrom
add-tag-workflow

Conversation

@divyansh42

Copy link
Copy Markdown
Collaborator

Add a manually triggered workflow that creates version tags on all downstream repos after a minor/patch release. Enables backtracking changes deployed to customer environments and identifying revert points when issues arise.

Features:

  • Auto-derives tag from release config or accepts manual override
  • Configurable branch and repo filtering (comma-separated)
  • Dry-run mode for safe validation
  • Outputs summary table in GitHub Step Summary

Assisted-by: Claude Opus 4 (via Cursor)

Add a manually triggered workflow that creates version tags on all
downstream repos after a minor/patch release. Enables backtracking
changes deployed to customer environments and identifying revert
points when issues arise.

Features:
- Auto-derives tag from release config or accepts manual override
- Configurable branch and repo filtering (comma-separated)
- Dry-run mode for safe validation
- Outputs summary table in GitHub Step Summary

Signed-off-by: divyansh42 <diagrawa@redhat.com>
Assisted-by: Claude Opus 4 (via Cursor)
fi

# Get the SHA of the branch HEAD
SHA=$(gh api "repos/$FULL_REPO/git/ref/heads/$BRANCH" --jq '.object.sha' 2>/dev/null)

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.

should be reading the commit sha from released snapshot not from the head of the repo.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

So in that case, we will need to provide the released snapshot and we should have the logic to find the commit sha of the individual components?

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.

Agree with Pramod's point, user should be able to derive that using the snapshot. I have a script for doing this if you need to reference or plan how to integrate it.

Snapshot: openshift-pipelines-core-1-22-20260630-164711-000-pi
Created:  2026-06-30 22:26 IST

Repo                                               Revision       Components
--------------------------------------------------------------------------------
openshift-pipelines/operator                       a8570514dd8f   3
openshift-pipelines/p12n-console-plugin            11c1ea728bb0   1
openshift-pipelines/p12n-console-plugin-pf5        5f871b8eb87f   1
openshift-pipelines/p12n-manual-approval-gate      f25d0d7642f0   2
openshift-pipelines/p12n-multicluster-proxy-aae    86475aae6abe   1
openshift-pipelines/p12n-opc                       75c5770be7ad   1
openshift-pipelines/p12n-syncer-service            b029f0528ca8   1
openshift-pipelines/p12n-tekton-caches             35d13ca95e59   1
openshift-pipelines/pac-downstream                 bd2efb6bac78   4
openshift-pipelines/serve-tkn-cl                   a510d8905687   1
openshift-pipelines/tekton-kueue                   9e2bc49b0eb2   1
openshift-pipelines/tektoncd-chains                5ce5347c8544   1
openshift-pipelines/tektoncd-cl                    3f9d353d6e2b   1
openshift-pipelines/tektoncd-git-clone             f4ea3d89f9db   1
openshift-pipelines/tektoncd-hub                   410f9709ee1d   2
openshift-pipelines/tektoncd-hub                   ff21b02885dc   1
openshift-pipelines/tektoncd-pipeline              1774b2fdc8f3   8
openshift-pipelines/tektoncd-pruner                68bfea16b601   2
openshift-pipelines/tektoncd-results               23029ec34482   3
openshift-pipelines/tektoncd-triggers              8abaa965abcc   4

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.

Lets not invest more on github workflows. we should go by the plan
that way we can reuse the things we develop

@divyansh42

Copy link
Copy Markdown
Collaborator Author

/hold
We will resume once we have the one click patch automation in place

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants