Skip to content

NO-JIRA: [bot] Synchronize versions of the downstream components #2712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 29, 2025
Merged

NO-JIRA: [bot] Synchronize versions of the downstream components #2712

merged 1 commit into from
Oct 29, 2025

Conversation

@openshift-monitoring-bot
Copy link

@openshift-monitoring-bot openshift-monitoring-bot bot commented Oct 15, 2025

Description

This pull request updates jsonnet/versions.yaml to match with the already in use downstream versions of the monitoring components.

Based on that file, it regenerates the assets to update some metadata (mainly the app.kubernetes.io/version annotation) attached to some of the resources and update other placeholders.

It is safe to merge this change (provided that the CI jobs pass).

If you wish to perform this manually, execute the following commands from cluster-monitoring-operator repository:

make versions
make generate

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 15, 2025

@openshift-monitoring-bot[bot]: This pull request explicitly references no jira issue.

In response to this:

Description

This pull request updates jsonnet/versions.yaml to match with the already in use downstream versions of the monitoring components.

Based on that file, it regenerates the assets to update some metadata (mainly the app.kubernetes.io/version annotation) attached to some of the resources and update other placeholders.

It is safe to merge this change (provided that the CI jobs pass).

If you wish to perform this manually, execute the following commands from cluster-monitoring-operator repository:

make versions
make generate

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 15, 2025
@openshift-ci openshift-ci bot requested review from machine424 and slashpai October 15, 2025 00:57
simonpasquier
simonpasquier reviewed Oct 15, 2025
View reviewed changes
Copy link
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/verified by existing tests

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 15, 2025
@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 16, 2025

/verified by existing tests

@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 16, 2025

/retest-required

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 16, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 16, 2025

@simonpasquier: This PR has been marked as verified by existing tests.

In response to this:

/verified by existing tests

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 openshift-eng/jira-lifecycle-plugin repository.

@slashpai
Copy link
Member

slashpai commented Oct 16, 2025

/test e2e-aws-ovn-techpreview

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 16, 2025

/retest-required

Remaining retests: 0 against base HEAD e9126a5 and 2 for PR HEAD 25a82b8 in total

@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-main-versions-generate branch from 25a82b8 to 364a228 Compare October 17, 2025 00:57
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Oct 17, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 17, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2025
@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 17, 2025

/verified by existing tests

@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 17, 2025

/skip
/retest-required

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 17, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 17, 2025

@simonpasquier: This PR has been marked as verified by existing tests.

In response to this:

/verified by existing tests

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 17, 2025

/retest-required

Remaining retests: 0 against base HEAD e9126a5 and 2 for PR HEAD 364a228 in total

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 20, 2025

/retest-required

Remaining retests: 0 against base HEAD ffeace4 and 1 for PR HEAD 364a228 in total

@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-main-versions-generate branch from 364a228 to a98366c Compare October 21, 2025 00:58
@openshift-ci-robot openshift-ci-robot removed the verified Signifies that the PR passed pre-merge verification criteria label Oct 21, 2025
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 21, 2025
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-main-versions-generate branch from a98366c to 62e2104 Compare October 23, 2025 00:58
@github-actions
NO-JIRA: [bot] Synchronize versions of the downstream components
abe8422 
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@monitoring-commit-bot monitoring-commit-bot bot force-pushed the automated-updates-main-versions-generate branch from 62e2104 to abe8422 Compare October 24, 2025 00:52
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 24, 2025 •
edited
Loading

@openshift-monitoring-bot[bot]: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/okd-scos-e2e-aws-ovn abe8422 link false /test okd-scos-e2e-aws-ovn

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

simonpasquier
simonpasquier reviewed Oct 29, 2025
View reviewed changes
Copy link
Contributor

@simonpasquier simonpasquier left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve
/verified by tests

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 29, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 29, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: openshift-monitoring-bot[bot], simonpasquier

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

The pull request process is described 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

@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 29, 2025

/skip
/retest-required

@simonpasquier
Copy link
Contributor

simonpasquier commented Oct 29, 2025

/verified by tests

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 29, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Oct 29, 2025

@simonpasquier: This PR has been marked as verified by tests.

In response to this:

/verified by tests

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-merge-bot openshift-merge-bot bot merged commit e21488a into openshift:main Oct 29, 2025
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@simonpasquier simonpasquier simonpasquier left review comments

@machine424 machine424 Awaiting requested review from machine424

@slashpai slashpai Awaiting requested review from slashpai

Assignees

@simonpasquier simonpasquier

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@openshift-ci-robot @simonpasquier @slashpai