feat(deps): update helm-install-image docker tag to v0.560-helm-3.17.0-kube-1.31.6-alpine-3.21.2
This MR contains the following updates:
Package | Update | Change |
---|---|---|
helm-install-image | minor |
v0.557-helm-3.17.0-kube-1.31.5-alpine-3.21.2 -> v0.560-helm-3.17.0-kube-1.31.6-alpine-3.21.2
|
MR created with the help of gitlab-org/frontend/renovate-gitlab-bot
Release Notes
gitlab-org/cluster-integration/helm-install-image (helm-install-image)
v0.560-helm-3.17.0-kube-1.31.6-alpine-3.21.2
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.
Merge request reports
Activity
Renovate Comment
What are the next steps?
If you have been assigned as a reviewer to this Merge Request, please review this Merge Request with the same scrutiny as any community contribution:
-
Ensure that the dependencies updated meet our standards:
- Security: Dependencies do not contain malicious code
- Performance: Dependencies do not bloat the application code or prolong CI times unnecessarily
- Stability: Pipelines are passing
-
Review the changes introduced by the version upgrade. Consider using https://my.diffend.io to compare the two versions in case the updated dependency is either a Ruby Gem or a Node.js package, for example to compare
pg_query
2.1.0
and2.1.4
. -
Check if
bundle install
works locally, in the context of GDK. -
If tests are passing and you've reviewed the updated dependencies, execute pipelines in the context of the main project
This MR is created from a fork, therefore not all jobs (e.g. Danger) might have been executed. Instead of hitting MWPS right away, you might want to wait until the pipeline you've just triggered finished.
Note: This might not be available in projects, in that case merging right away is an option
-
Assign the current milestone to the MR
-
Merge away!
Troubleshooting
We have assembled some FAQs to help reviewers of these kind of merge requests.
Improve this message – The JSON comment below is for automation purposes.
{"labels":["group::environments","devops::deploy","section::cd","type::maintenance","maintenance::dependency"],"assignees":["gitlab-dependency-update-bot"],"reviewers":["Alexand","takax","tigerwnz","timofurrer"]}
-
added 1 commit
- dd439f9a - feat(deps): update helm-install-image docker tag to v0.560-helm-3.17.0-kube-1.31.6-alpine-3.21.2
mentioned in issue #217
requested review from @Alexand and @timofurrer
assigned to @gitlab-dependency-update-bot
changed milestone to %17.10
changed milestone to %17.9
started a merge train
Reviewer roulette
Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category and by a maintainer in all other categories.
To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.
To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.
Once you've decided who will review this merge request, mention them as you normally would! Danger does not automatically notify them for you.
Reviewer Maintainer No reviewer available @takax
(UTC+9)
If needed, you can retry the
danger-review
job that generated this comment.Generated by
Dangermentioned in commit 49b0012c
added automation:bot-authored label