Skip to content

chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775681336#694

Open
red-hat-konflux[bot] wants to merge 1 commit intorelease/1.2.zfrom
konflux/mintmaker/release/1.2.z/registry.access.redhat.com-ubi10-go-toolset-10.x
Open

chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775681336#694
red-hat-konflux[bot] wants to merge 1 commit intorelease/1.2.zfrom
konflux/mintmaker/release/1.2.z/registry.access.redhat.com-ubi10-go-toolset-10.x

Conversation

@red-hat-konflux
Copy link
Copy Markdown
Contributor

@red-hat-konflux red-hat-konflux bot commented Apr 3, 2026

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi10/go-toolset stage patch 10.110.1-1775681336

Warning

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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
Copy link
Copy Markdown

sourcery-ai bot commented Apr 3, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the Red Hat UBI10 go-toolset container image used in the rhtpa operator Dockerfile to a newer patch-tagged version.

File-Level Changes

Change Details Files
Bump the ubi10/go-toolset base image tag to a specific patch version for the rhtpa operator build.
  • Change the go-toolset image tag from 10.1 to 10.1-1775091538 in the operator Dockerfile stage definition.
  • Ensure the build continues to use the same image source registry and repository while pinning to a more specific tag.
Dockerfile.rhtpa-operator.rh

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

Copy link
Copy Markdown

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

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


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775091538 chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775437069 Apr 6, 2026
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release/1.2.z/registry.access.redhat.com-ubi10-go-toolset-10.x branch from abc192a to f0da55b Compare April 6, 2026 06:42
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775437069 chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775574742 Apr 7, 2026
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release/1.2.z/registry.access.redhat.com-ubi10-go-toolset-10.x branch from f0da55b to b9378a0 Compare April 7, 2026 22:30
…r tag to v10.1-1775681336

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775574742 chore(deps): update registry.access.redhat.com/ubi10/go-toolset docker tag to v10.1-1775681336 Apr 9, 2026
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release/1.2.z/registry.access.redhat.com-ubi10-go-toolset-10.x branch from b9378a0 to 5140a4e Compare April 9, 2026 02:32
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.

0 participants