Skip to content

Conversation

red-hat-konflux[bot]
Copy link
Contributor

@red-hat-konflux red-hat-konflux bot commented Aug 15, 2025

This PR contains the following updates:

Package Type Update Change
registry.access.redhat.com/ubi9/nodejs-22 stage patch 9.6-1755015241 -> 9.6-1756815546

Configuration

📅 Schedule: Branch creation - "before 5am" (UTC), 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.

This PR has been generated by MintMaker (powered by Renovate Bot).

@red-hat-konflux red-hat-konflux bot added the dependencies Pull requests that update a dependency file label Aug 15, 2025
Copy link

openshift-ci bot commented Aug 15, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ronensc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

openshift-ci bot commented Aug 15, 2025

Hi @red-hat-konflux[bot]. Thanks for your PR.

I'm waiting for a netobserv member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-1.9/registry.access.redhat.com-ubi9-nodejs-22-9.x branch from 8218827 to 508c87e Compare August 21, 2025 00:20
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi9/nodejs-22 docker tag to v9.6-1755075210 chore(deps): update registry.access.redhat.com/ubi9/nodejs-22 docker tag to v9.6-1755720914 Aug 21, 2025
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-1.9/registry.access.redhat.com-ubi9-nodejs-22-9.x branch from 508c87e to 971d7d7 Compare August 26, 2025 00:19
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi9/nodejs-22 docker tag to v9.6-1755720914 chore(deps): update registry.access.redhat.com/ubi9/nodejs-22 docker tag to v9.6-1756109943 Aug 26, 2025
…tag to v9.6-1756815546

Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
@red-hat-konflux red-hat-konflux bot force-pushed the konflux/mintmaker/release-1.9/registry.access.redhat.com-ubi9-nodejs-22-9.x branch from 971d7d7 to f9c9dfb Compare September 3, 2025 00:17
@red-hat-konflux red-hat-konflux bot changed the title chore(deps): update registry.access.redhat.com/ubi9/nodejs-22 docker tag to v9.6-1756109943 chore(deps): update registry.access.redhat.com/ubi9/nodejs-22 docker tag to v9.6-1756815546 Sep 3, 2025
@openshift-ci openshift-ci bot added the lgtm label Sep 4, 2025
@OlivierCazade OlivierCazade merged commit b851b3a into release-1.9 Sep 4, 2025
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file lgtm needs-ok-to-test

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant