Skip to content

chore(go.mod): update github.com/prometheus/prometheus dep #2550

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
Draft
wants to merge 2 commits into
base: main
Choose a base branch
from
Draft

chore(go.mod): update github.com/prometheus/prometheus dep #2550

wants to merge 2 commits into from

Conversation

machine424
Copy link
Contributor

also

chore(go.mod): update go and toolchain versions

  • I added CHANGELOG entry for this change.
  • No user facing changes, so no entry in CHANGELOG was needed.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 6, 2025
@machine424
Copy link
Contributor Author

/retest images

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 7, 2025

@machine424: The /retest command does not accept any targets.
The following commands are available to trigger required jobs:

/test e2e-agnostic-operator

/test e2e-aws-ovn

/test e2e-aws-ovn-techpreview

/test e2e-aws-ovn-upgrade

/test e2e-hypershift-conformance

/test generate

/test go-fmt

/test golangci-lint

/test images

/test jsonnet-fmt

/test rules

/test shellcheck

/test unit

/test vendor

/test verify

The following commands are available to trigger optional jobs:

/test e2e-aws-ovn-single-node

/test okd-scos-e2e-aws-ovn

/test okd-scos-images

/test versions

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-cluster-monitoring-operator-master-e2e-agnostic-operator

pull-ci-openshift-cluster-monitoring-operator-master-e2e-aws-ovn

pull-ci-openshift-cluster-monitoring-operator-master-e2e-aws-ovn-single-node

pull-ci-openshift-cluster-monitoring-operator-master-e2e-aws-ovn-techpreview

pull-ci-openshift-cluster-monitoring-operator-master-e2e-aws-ovn-upgrade

pull-ci-openshift-cluster-monitoring-operator-master-e2e-hypershift-conformance

pull-ci-openshift-cluster-monitoring-operator-master-generate

pull-ci-openshift-cluster-monitoring-operator-master-go-fmt

pull-ci-openshift-cluster-monitoring-operator-master-golangci-lint

pull-ci-openshift-cluster-monitoring-operator-master-images

pull-ci-openshift-cluster-monitoring-operator-master-jsonnet-fmt

pull-ci-openshift-cluster-monitoring-operator-master-okd-scos-e2e-aws-ovn

pull-ci-openshift-cluster-monitoring-operator-master-rules

pull-ci-openshift-cluster-monitoring-operator-master-shellcheck

pull-ci-openshift-cluster-monitoring-operator-master-unit

pull-ci-openshift-cluster-monitoring-operator-master-vendor

pull-ci-openshift-cluster-monitoring-operator-master-verify

pull-ci-openshift-cluster-monitoring-operator-master-versions

In response to this:

/retest images

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.

@machine424
Copy link
Contributor Author

/test images

@juzhao
Copy link
Contributor

juzhao commented Jan 9, 2025

/retest-required

@machine424 machine424 marked this pull request as draft January 9, 2025 09:40
@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jan 9, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 17, 2025 •
edited
Loading

@machine424: The following tests 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/e2e-aws-ovn-single-node bab8b64 link false /test e2e-aws-ovn-single-node
ci/prow/versions bab8b64 link false /test versions

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.

@machine424
Copy link
Contributor Author

/retest-required

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Apr 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: machine424

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

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 4, 2025
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 4, 2025
@openshift-merge-robot
Copy link
Contributor

PR needs rebase.

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.

@openshift-bot
Copy link
Contributor

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@danielmellado danielmellado Awaiting requested review from danielmellado

@marioferh marioferh Awaiting requested review from marioferh

Assignees
No one assigned
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@machine424 @juzhao @openshift-bot @openshift-merge-robot