chore: make update#2704
Merged
simonpasquier merged 1 commit intoprometheus-operator:mainfrom Jul 29, 2025
Merged
Conversation
Member
|
For some reason, the CI is failing. Please investigate this issue and make the necessary changes to get the merge approved. Thanks for looking into this! |
rexagod
force-pushed
the
make-update
branch
2 times, most recently
from
d0bb61a to
b74cf84
Compare
Signed-off-by: Pranshu Srivastava <rexagod@gmail.com>
Contributor
Author
|
I believe this should be good now: https://github.com/rexagod/kube-prometheus/actions/runs/16577300578 |
simonpasquier
approved these changes
Jul 29, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Bumping deps to pull in upstream changes.
Type of change
What type of changes does your code introduce to the kube-prometheus? Put an
xin the box that apply.CHANGE(fix or feature that would cause existing functionality to not work as expected)FEATURE(non-breaking change which adds functionality)BUGFIX(non-breaking change which fixes an issue)ENHANCEMENT(non-breaking change which improves existing functionality)NONE(if none of the other choices apply. Example, tooling, build system, CI, docs, etc.)