alexlebens/infrastructure
1
0
Fork 0
Code Issues 1 Pull Requests 7 Actions Packages Projects Releases Wiki Activity

Update Helm release volsync to v0.13.0 #946

Merged
alexlebens merged 1 commits from renovate/volsync-0.x into main 2025-07-16 18:30:33 +00:00
Conversation 0 Commits 1 Files Changed 1 +1 -1
renovate-bot commented 2025-07-16 18:01:44 +00:00
Collaborator
Copy Link

This PR contains the following updates:

Package Update Change
volsync (source) minor 0.12.1 -> 0.13.0

Release Notes

backube/volsync (volsync)

v0.13.0

Compare Source

Changed
  • Multi-arch volsync image published in quay.io, will include amd64 as usual as well as arm64
  • Restic updated to v0.18.0
  • Syncthing updated to v1.29.7
Fixed
  • Fix restic cache PVC name collision if replicationsource and
    replicationdestination have the same name and are in the same
    namespace
Security
  • kube-rbac-proxy upgraded to v0.19.2

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 has been generated by Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [volsync](https://volsync.readthedocs.io/) ([source](https://github.com/backube/volsync)) | minor | `0.12.1` -> `0.13.0` | --- ### Release Notes <details> <summary>backube/volsync (volsync)</summary> ### [`v0.13.0`](https://github.com/backube/volsync/releases/tag/v0.13.0) [Compare Source](https://github.com/backube/volsync/compare/v0.12.1...v0.13.0) ##### Changed - Multi-arch volsync image published in quay.io, will include amd64 as usual as well as arm64 - Restic updated to v0.18.0 - Syncthing updated to v1.29.7 ##### Fixed - Fix restic cache PVC name collision if replicationsource and replicationdestination have the same name and are in the same namespace ##### Security - kube-rbac-proxy upgraded to v0.19.2 </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 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. --- - [ ] <!-- 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:eyJjcmVhdGVkSW5WZXIiOiI0MS4zNS4xIiwidXBkYXRlZEluVmVyIjoiNDEuMzUuMSIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiY2hhcnQiXX0=-->
renovate-bot added the
chart
 label 2025-07-16 18:01:44 +00:00
renovate-bot added 1 commit 2025-07-16 18:01:45 +00:00
Update Helm release volsync to v0.13.0
All checks were successful
renovate/stability-days Updates have met minimum release age requirement
Details
lint-test-helm / helm-lint (pull_request) Successful in 11s
Details
605ce5760e
alexlebens merged commit cf1761d32e into main 2025-07-16 18:30:33 +00:00
alexlebens deleted branch renovate/volsync-0.x 2025-07-16 18:30:33 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Renovate
Issue generated by Renovate.
automerge
This PR will be automerged by Renovate.
chart
Chart update generated by Renovate.
image
Image update generated by Renovate.
stale
PR or Issue that has not been updated recently.
No Label
chart
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
gitea-bot renovate-bot alexlebens
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: alexlebens/infrastructure#946
No description provided.
Delete Branch "renovate/volsync-0.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?