search

pascaliske / infrastructure

Flux based GitOps repository for my home lab infrastructure.
https://k8s.pascaliske.dev
MIT License
59 stars 3 forks source link

chore(deps): update rancher/system-upgrade-controller docker tag to v0.14.1 #1960

Closed renovate[bot] closed 4 weeks ago

renovate[bot] commented 1 month ago

This PR contains the following updates:

Package Type Update Change
rancher/system-upgrade-controller minor v0.13.4 -> v0.14.1
rancher/system-upgrade-controller Kustomization minor v0.13.4 -> v0.14.1

Release Notes

rancher/system-upgrade-controller (rancher/system-upgrade-controller) ### [`v0.14.1`](https://redirect.github.com/rancher/system-upgrade-controller/releases/tag/v0.14.1) [Compare Source](https://redirect.github.com/rancher/system-upgrade-controller/compare/v0.14.0-rc1...v0.14.1) ##### What's Changed - Revert "fix(kustomize): Deploy latest system-upgrade-controller" by [@​onno204](https://redirect.github.com/onno204) in [https://github.com/rancher/system-upgrade-controller/pull/304](https://redirect.github.com/rancher/system-upgrade-controller/pull/304) ##### New Contributors - [@​onno204](https://redirect.github.com/onno204) made their first contribution in [https://github.com/rancher/system-upgrade-controller/pull/304](https://redirect.github.com/rancher/system-upgrade-controller/pull/304) **Full Changelog**: https://github.com/rancher/system-upgrade-controller/compare/v0.14.0...v0.14.1 ### [`v0.14.0`](https://redirect.github.com/rancher/system-upgrade-controller/releases/tag/v0.14.0) [Compare Source](https://redirect.github.com/rancher/system-upgrade-controller/compare/v0.13.4...v0.14.0-rc1) ##### What's Changed - fix: Drop unneeded reorder surpression by [@​SISheogorath](https://redirect.github.com/SISheogorath) in [https://github.com/rancher/system-upgrade-controller/pull/296](https://redirect.github.com/rancher/system-upgrade-controller/pull/296) - Update/fix README kustomize command by [@​SISheogorath](https://redirect.github.com/SISheogorath) in [https://github.com/rancher/system-upgrade-controller/pull/297](https://redirect.github.com/rancher/system-upgrade-controller/pull/297) - Add GHA workflows by [@​bfbachmann](https://redirect.github.com/bfbachmann) in [https://github.com/rancher/system-upgrade-controller/pull/311](https://redirect.github.com/rancher/system-upgrade-controller/pull/311) - Upgrade outdated golang dependencies by [@​harsimranmaan](https://redirect.github.com/harsimranmaan) in [https://github.com/rancher/system-upgrade-controller/pull/326](https://redirect.github.com/rancher/system-upgrade-controller/pull/326) - feat: allow pod replacement policy override by [@​buroa](https://redirect.github.com/buroa) in [https://github.com/rancher/system-upgrade-controller/pull/328](https://redirect.github.com/rancher/system-upgrade-controller/pull/328) - fix: system-upgrade-controller-drainer: add missing delete permission for pods in clusterrole by [@​damdo](https://redirect.github.com/damdo) in [https://github.com/rancher/system-upgrade-controller/pull/320](https://redirect.github.com/rancher/system-upgrade-controller/pull/320) - Bump golang.org/x/net from 0.17.0 to 0.23.0 in /pkg/apis by [@​dependabot](https://redirect.github.com/dependabot) in [https://github.com/rancher/system-upgrade-controller/pull/307](https://redirect.github.com/rancher/system-upgrade-controller/pull/307) - Fix GHA release workflow by [@​brandond](https://redirect.github.com/brandond) in [https://github.com/rancher/system-upgrade-controller/pull/330](https://redirect.github.com/rancher/system-upgrade-controller/pull/330) - Fix image tag by [@​brandond](https://redirect.github.com/brandond) in [https://github.com/rancher/system-upgrade-controller/pull/331](https://redirect.github.com/rancher/system-upgrade-controller/pull/331) - Fix artifact permissions by [@​brandond](https://redirect.github.com/brandond) in [https://github.com/rancher/system-upgrade-controller/pull/332](https://redirect.github.com/rancher/system-upgrade-controller/pull/332) ##### New Contributors - [@​bfbachmann](https://redirect.github.com/bfbachmann) made their first contribution in [https://github.com/rancher/system-upgrade-controller/pull/311](https://redirect.github.com/rancher/system-upgrade-controller/pull/311) - [@​harsimranmaan](https://redirect.github.com/harsimranmaan) made their first contribution in [https://github.com/rancher/system-upgrade-controller/pull/326](https://redirect.github.com/rancher/system-upgrade-controller/pull/326) - [@​damdo](https://redirect.github.com/damdo) made their first contribution in [https://github.com/rancher/system-upgrade-controller/pull/320](https://redirect.github.com/rancher/system-upgrade-controller/pull/320) **Full Changelog**: https://github.com/rancher/system-upgrade-controller/compare/v0.13.4...v0.14.0

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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

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

coderabbitai[bot] commented 1 month ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.