chore(deps): update dependency sighupio/furyctl to v0.30.1 #8732
Conversation
This file contains 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
nicholasdille-bot
approved these changes
Nov 29, 2024
🔍 Vulnerabilities of
|
| digest | sha256:13b74ed548cf7c9f15c91022e3f581bff1b1632cbb6f3161302661e67ca87037 |
| vulnerabilities |     |
| platform | linux/amd64 |
| size | 15 MB |
| packages | 122 |
|
Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/12088167712. |
|
PR is clean and can be merged. See https://github.com/uniget-org/tools/actions/runs/12088167712. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR contains the following updates:
0.30.0->0.30.1Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
sighupio/furyctl (sighupio/furyctl)
v0.30.1Compare Source
Changelog
e8fb961Merge pull request #558 from sighupio/fix/upgrades-ingressv3-no-monitoring9e94e3dfix(upgrades): delete monitoring resources when enabled only The upgrade scripts for migrating to ingress v3 tried to delete resources that are not needed anymore even when they may not exist. The flag --ignore-not-found works for native resources, but fails when trying to delete resources that the CRDs are not deployed to the cluster, so the kind is unknown for the API.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.
This PR has been generated by Renovate Bot.