chore(deps): update dependency github.com/redhatinsights/konflux-pipelines to v1.72.0 (foreman-3.16)

[red-hat-konflux]

This PR contains the following updates:

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

---

Release Notes

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

v1.72.0

Compare Source

What's Changed

• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​261
• chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v1.26.5-1786522985 by @​red-hat-konflux[bot] in #​262
• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​264
• chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v1.26.5-1787080706 by @​red-hat-konflux[bot] in #​265

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

v1.71.0

Compare Source

What's Changed

• chore(deps): update registry.access.redhat.com/ubi9/go-toolset docker tag to v1.26.4-1783442369 by @​red-hat-konflux[bot] in #​249
• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​252
• Docs/e2e sidecar best practices (RHCLOUD-49182) by @​catastrophe-brandon in #​253
• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​255
• fix(ci): change test-scripts-pipeline-run and point to this repo by @​patchkez in #​257
• feat(renovate): use official postTask for RPM refresh and set recreate to always by @​vkrizan in #​258
• Fix ref in test script pipeline by @​patchkez in #​259
• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​256
• chore(deps): update konflux references by @​red-hat-konflux[bot] in #​260

Full Changelog: RedHatInsights/konflux-pipelines@v1.70.0...v1.71.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• 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.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Tekton Pipelines-as-Code configuration to use konflux-pipelines v1.71.0 instead of v1.70.0 for Yuptoo-related pipelines on main and foreman-3.16 branches.

Flow diagram for updated konflux-pipelines version in Tekton Pipelines-as-Code

flowchart LR
    Developer[[Git push / PR]] --> Repo[GitRepository yuptoo]
    Repo --> PAC[PipelinesAsCode]
    PAC -->|pull_request foreman-3_16 / main| PipelineTemplate
    subgraph PipelineTemplate
        V1710[docker-build-oci-ta v1_70_0] -.old reference.- PAC
        V1711[docker-build-oci-ta v1_71_0]
    end
    PAC -->|uses| V1711
    V1711 --> TektonPipelineRun[Tekton PipelineRun]
    TektonPipelineRun --> ImageRegistry[Container Image Registry]

Loading

File-Level Changes

Change	Details	Files
Bump referenced konflux-pipelines Tekton pipeline definition from v1.70.0 to v1.71.0 for Yuptoo pull-request and push workflows.	Update pipelinesascode.tekton.dev/pipeline annotation URLs in foreman-3.16 pull-request pipeline to point to v1.71.0 docker-build-oci-ta.yaml. Update pipelinesascode.tekton.dev/pipeline annotation URLs in foreman-3.16 push pipeline to point to v1.71.0 docker-build-oci-ta.yaml. Update pipelinesascode.tekton.dev/pipeline annotation URLs in main-branch pull-request pipeline to point to v1.71.0 docker-build-oci-ta.yaml. Update pipelinesascode.tekton.dev/pipeline annotation URLs in main-branch push pipeline to point to v1.71.0 docker-build-oci-ta.yaml.	.tekton/iop-yuptoo-sat-6-18-pull-request.yaml .tekton/iop-yuptoo-sat-6-18-push.yaml .tekton/yuptoo-pull-request.yaml .tekton/yuptoo-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 left some high level feedback:

• Consider centralizing the konflux-pipelines version (e.g., via a shared value or template) so updating to new releases doesn’t require touching multiple Tekton YAML files individually.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider centralizing the konflux-pipelines version (e.g., via a shared value or template) so updating to new releases doesn’t require touching multiple Tekton YAML files individually.

---

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.}