Skip to content
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

Update ghcr.io/fluxcd/kustomize-controller Docker tag to v1.3.0 - autoclosed #30

Closed

Conversation

MathiasPius
Copy link
Owner

This PR contains the following updates:

Package Update Change
ghcr.io/fluxcd/kustomize-controller minor v1.2.2 -> v1.3.0

Release Notes

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

v1.3.0

Compare Source

Changelog

v1.3.0 changelog

Container images

  • docker.io/fluxcd/kustomize-controller:v1.3.0
  • ghcr.io/fluxcd/kustomize-controller:v1.3.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 this update again.


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

This PR has been generated by Renovate Bot.

@MathiasPius MathiasPius changed the title Update ghcr.io/fluxcd/kustomize-controller Docker tag to v1.3.0 Update ghcr.io/fluxcd/kustomize-controller Docker tag to v1.3.0 - autoclosed May 14, 2024
@MathiasPius MathiasPius deleted the renovate/ghcr.io-fluxcd-kustomize-controller-1.x branch May 14, 2024 21:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants