Skip to content

Update Helm release kube-prometheus-stack to v71.2.0 #2816

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.

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

Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 2, 2025

This PR contains the following updates:

Package Update Change
kube-prometheus-stack (source) minor 71.1.0 -> 71.2.0

Release Notes

prometheus-community/helm-charts (kube-prometheus-stack)

v71.2.0

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

Full Changelog: prometheus-community/helm-charts@prometheus-node-exporter-4.46.0...kube-prometheus-stack-71.2.0

v71.1.1

Compare Source

kube-prometheus-stack collects Kubernetes manifests, Grafana dashboards, and Prometheus rules combined with documentation and scripts to provide easy to operate end-to-end Kubernetes cluster monitoring with Prometheus using the Prometheus Operator.

What's Changed

Full Changelog: prometheus-community/helm-charts@prometheus-nginx-exporter-1.4.0...kube-prometheus-stack-71.1.1


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

This PR was generated by Mend Renovate. View the repository job log.

Copy link

qodo-merge-pro bot commented May 2, 2025

CI Feedback 🧐

(Feedback updated until commit a134f2c)

A test triggered by this PR failed. Here is an AI-generated analysis of the failure:

Action: Rerun workflow when failure

Failed stage: Authenticate GitHub CLI for PR [❌]

Failure summary:

The action failed because the GitHub CLI authentication failed with the error: "missing required
scope 'read:org'". The token provided in the GH_CLI_TOKEN_PR environment variable does not have the
necessary permissions to perform the required operations. Specifically, it's missing the 'read:org'
scope which is needed for the GitHub CLI to authenticate properly.

Relevant error logs:
1:  ##[group]Operating System
2:  Ubuntu
...

22:  Issues: write
23:  Metadata: read
24:  Models: read
25:  Packages: write
26:  Pages: write
27:  PullRequests: write
28:  RepositoryProjects: write
29:  SecurityEvents: write
30:  Statuses: write
31:  ##[endgroup]
32:  Secret source: Actions
33:  Prepare workflow directory
34:  Prepare all required actions
35:  Getting action download info
36:  Download action repository 'actions/checkout@main' (SHA:85e6279cec87321a52edac9c87bce653a07cf6c2)
37:  Complete job name: Rerun workflow when failure
38:  ##[group]Run actions/checkout@main
...

42:  ssh-strict: true
43:  ssh-user: git
44:  persist-credentials: true
45:  clean: true
46:  sparse-checkout-cone-mode: true
47:  fetch-depth: 1
48:  fetch-tags: false
49:  show-progress: true
50:  lfs: false
51:  submodules: false
52:  set-safe-directory: true
53:  env:
54:  GH_CLI_TOKEN: ***
55:  GH_CLI_TOKEN_PR: ***
56:  RUN_ID: 14886086929
57:  RERUN_FAILED_ONLY: true
58:  RUN_ATTEMPT: 1
...

113:  Or undo this operation with:
114:  git switch -
115:  Turn off this advice by setting config variable advice.detachedHead to false
116:  HEAD is now at 0bc20a4 Merge a134f2cfcc4e37af177bf606e495b5a2334e9580 into f7bc3fb7facd980ff4ac54945c578bcc2ff14588
117:  ##[endgroup]
118:  [command]/usr/bin/git log -1 --format=%H
119:  0bc20a4bfd38df721a9943592392fba527031239
120:  ##[group]Run sudo apt update
121:  �[36;1msudo apt update�[0m
122:  �[36;1msudo apt install gh�[0m
123:  shell: /usr/bin/bash -e {0}
124:  env:
125:  GH_CLI_TOKEN: ***
126:  GH_CLI_TOKEN_PR: ***
127:  RUN_ID: 14886086929
128:  RERUN_FAILED_ONLY: true
129:  RUN_ATTEMPT: 1
...

144:  Reading state information...
145:  19 packages can be upgraded. Run 'apt list --upgradable' to see them.
146:  WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
147:  Reading package lists...
148:  Building dependency tree...
149:  Reading state information...
150:  gh is already the newest version (2.72.0).
151:  0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
152:  ##[group]Run echo "$GH_CLI_TOKEN_PR" | gh auth login --with-token
153:  �[36;1mecho "$GH_CLI_TOKEN_PR" | gh auth login --with-token�[0m
154:  shell: /usr/bin/bash -e {0}
155:  env:
156:  GH_CLI_TOKEN: ***
157:  GH_CLI_TOKEN_PR: ***
158:  RUN_ID: 14886086929
159:  RERUN_FAILED_ONLY: true
160:  RUN_ATTEMPT: 1
161:  ##[endgroup]
162:  error validating token: missing required scope 'read:org'
163:  ##[error]Process completed with exit code 1.
164:  Post job cleanup.

@renovate renovate bot changed the title Update Helm release kube-prometheus-stack to v71.1.1 Update Helm release kube-prometheus-stack to v71.2.0 May 7, 2025
@renovate renovate bot force-pushed the renovate/kube-prometheus-stack-update branch from 2154666 to 21c1ca4 Compare May 7, 2025 14:31
Copy link
Contributor Author

renovate bot commented May 7, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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.

1 participant