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

chore(deps): update ghcr.io/pelotech/nidhogg docker tag to v0.5.3 #15

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 22, 2024

This PR contains the following updates:

Package Type Update Change
ghcr.io/pelotech/nidhogg Kustomization patch v0.5.1 -> v0.5.3

Release Notes

pelotech/nidhogg (ghcr.io/pelotech/nidhogg)

v0.5.3

Compare Source

What's Changed

New Contributors

Full Changelog: v0.5.2...v0.5.3

v0.5.2

Compare Source


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 this update again.


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

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

@renovate renovate bot force-pushed the renovate/ghcr.io-pelotech-nidhogg-0.x branch 3 times, most recently from 6ccc307 to 3132041 Compare August 13, 2024 19:35
@renovate renovate bot changed the title chore(deps): update ghcr.io/pelotech/nidhogg docker tag to v0.5.2 chore(deps): update ghcr.io/pelotech/nidhogg docker tag to v0.5.3 Aug 13, 2024
@renovate renovate bot force-pushed the renovate/ghcr.io-pelotech-nidhogg-0.x branch 8 times, most recently from 3338e31 to 7839dc2 Compare August 18, 2024 16:12
@renovate renovate bot force-pushed the renovate/ghcr.io-pelotech-nidhogg-0.x branch from 7839dc2 to 55e8c45 Compare September 23, 2024 19:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants