fix(release): apply project-specific OCI labels to images for Operator - #4079
TheDevCodingKen wants to merge 1 commit into
Conversation
|
[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 |
|
@TheDevCodingKen how did you raise the PR ? is there a human in the loop |
@jkhelil I'm the human in the loop. I manually made the changes locally based what was merged in the related background section of the main issue.
|
|
Pinging @infernus01 and @pramodbindal for approval |
|
/hold |
a672da1 to
65a1b5d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4079 +/- ##
==========================================
+ Coverage 25.40% 27.66% +2.26%
==========================================
Files 449 477 +28
Lines 23477 25469 +1992
==========================================
+ Hits 5964 7046 +1082
- Misses 16822 17699 +877
- Partials 691 724 +33
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Thanks change looks aligned with plumbing#3435, but we don’t merge agent-style PRs without a maintainer-owned follow-up. |

Changes
Fixes tektoncd/plumbing#3435
This updates the
tekton/build-publish-images-manifests.yamltask to explicitly pass project-specific OCI image labels (url,title, anddescription) to theko resolvecommands. This prevents the published Operator images from incorrectly inheriting OCI metadata from their base images.Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:
make test lintbefore submitting a PRRelease Notes