Fascinated/homelab
Archived
1
1
Fork 0
Code Issues 1 Pull Requests 9 Actions Activity

chore(deps): update ghcr.io/fluxcd/notification-controller docker tag to v1.4.0 #41

Open
renovate-bot wants to merge 1 commits from renovate/ghcr.io-fluxcd-notification-controller-1.x into master
pull from: renovate/ghcr.io-fluxcd-notification-controller-1.x
merge into: Fascinated:master
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2024-09-27 16:01:49 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
ghcr.io/fluxcd/notification-controller minor v1.3.0 -> v1.4.0

Release Notes

fluxcd/notification-controller (ghcr.io/fluxcd/notification-controller)

v1.4.0

Compare Source

Changelog

v1.4.0 changelog

Container images
  • docker.io/fluxcd/notification-controller:v1.4.0
  • ghcr.io/fluxcd/notification-controller:v1.4.0

Supported architectures: linux/amd64, linux/arm64 and linux/arm/v7.

The container images are built on GitHub hosted runners and are signed with cosign and GitHub OIDC.
To verify the images and their provenance (SLSA level 3), please see the security documentation.

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 these updates again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [ghcr.io/fluxcd/notification-controller](https://github.com/fluxcd/notification-controller) | minor | `v1.3.0` -> `v1.4.0` | --- ### Release Notes <details> <summary>fluxcd/notification-controller (ghcr.io/fluxcd/notification-controller)</summary> ### [`v1.4.0`](https://github.com/fluxcd/notification-controller/releases/tag/v1.4.0) [Compare Source](https://github.com/fluxcd/notification-controller/compare/v1.3.0...v1.4.0) ##### Changelog [v1.4.0 changelog](https://github.com/fluxcd/notification-controller/blob/v1.4.0/CHANGELOG.md) ##### Container images - `docker.io/fluxcd/notification-controller:v1.4.0` - `ghcr.io/fluxcd/notification-controller:v1.4.0` Supported architectures: `linux/amd64`, `linux/arm64` and `linux/arm/v7`. The container images are built on GitHub hosted runners and are signed with cosign and GitHub OIDC. To verify the images and their provenance (SLSA level 3), please see the [security documentation](https://fluxcd.io/flux/security/). </details> --- ### 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 these updates again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzOC4xMDAuMCIsInVwZGF0ZWRJblZlciI6IjM4LjEwMC4wIiwidGFyZ2V0QnJhbmNoIjoibWFzdGVyIiwibGFiZWxzIjpbXX0=-->
renovate-bot added 1 commit 2024-09-27 16:01:49 +00:00
This repo is archived. You cannot comment on pull requests.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something is not working
duplicate
This issue or pull request already exists
enhancement
New feature
help wanted
Need some help
invalid
Something is wrong
question
More information is needed
wontfix
This won't be fixed
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Fascinated/homelab#41
No description provided.
Delete Branch "renovate/ghcr.io-fluxcd-notification-controller-1.x"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?