Update dependency github.com/RedHatInsights/konflux-pipelines to v1.73.0

[red-hat-konflux]

This PR contains the following updates:

Package	Type	Update	Change
github.com/RedHatInsights/konflux-pipelines	tekton-annotation	minor	v1.72.0 → v1.73.0

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

RedHatInsights/konflux-pipelines (github.com/RedHatInsights/konflux-pipelines)

v1.73.0

Compare Source

What's Changed

• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​267
• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​269

Full Changelog: RedHatInsights/konflux-pipelines@v1.72.0...v1.73.0

---

Configuration

📅 Schedule: (in timezone Europe/Prague)

• Branch creation
  • Between 05:00 AM and 11:59 PM, only on Saturday (* 5-23 * * 6)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

Summary by Sourcery

Chores:

• Update Tekton pipeline references to the Konflux pipelines v1.73.0 release.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Both Patchman Tekton triggers now fetch docker-build-oci-ta.yaml from Konflux Pipelines v1.73.0 instead of v1.72.0; review the upstream dependency changes and verify pull request and push pipeline execution before relying on automerge.

File-Level Changes

Change	Details	Files
Update the referenced Konflux Tekton pipeline to the v1.73.0 release.	Change the pull request pipeline annotation from v1.72.0 to v1.73.0. Change the push pipeline annotation from v1.72.0 to v1.73.0. Review the upstream release changes and validate both event paths against the updated pipeline definition.	.tekton/patchman-engine-pull-request.yaml .tekton/patchman-engine-push.yaml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.07%. Comparing base (cbc54e3) to head (30d5e86).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2319   +/-   ##
=======================================
  Coverage   59.07%   59.07%           
=======================================
  Files         150      150           
  Lines        9614     9614           
=======================================
  Hits         5679     5679           
  Misses       3341     3341           
  Partials      594      594           

Flag	Coverage Δ
unittests	59.07% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.