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

feat(container): update volsync group ( 0.8.0 → 0.9.1 ) #864

Merged
merged 1 commit into from
Apr 13, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 21, 2024

Mend Renovate

This PR contains the following updates:

Package Update Change
ghcr.io/onedr0p/volsync (source) minor 0.8.0 -> 0.9.1
volsync (source) minor 0.8.0 -> 0.9.1

Release Notes

backube/volsync (ghcr.io/onedr0p/volsync)

v0.9.1

Compare Source

Fixed
  • Allow restic restore from empty or non-initialized path
  • Ignore lost+found on restic backup when checking for empty source volume

v0.9.0

Compare Source

Changed
  • Syncthing upgraded to v1.27.3
  • Restic upgraded to v0.16.4
  • Updated release to build on golang 1.21
Added
  • Allow customization of resource requirements and limits on mover job containers
  • Include additional restic environment variables from the restic secret
    (RESTIC_REST_USERNAME, RESTIC_REST_PASSWORD, AZURE_ENDPOINT_SUFFIX)
  • Copy trigger pvc annotations. Allows copy-trigger annotations on the pvc to
    pause/trigger snapshots or clones in a sync
  • Include all RCLONE_ env vars from the rclone secret to be set in the rclone
    mover job
Fixed
  • Exclude lost+found for restic backups
  • Check if ipv6 is enabled before assigning 'STUNNEL_LISTEN_PORT' in mover-rsync-tls
    server script

v0.8.1

Compare Source

Changed
  • Updated release to build on golang 1.21
Fixed
  • Capture error on restic restore when connecting to repository

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 Mend Renovate. View repository job log here.

@smbonn2005
Copy link
Owner

held pending 0.9.1 per backube/volsync#1172

@renovate renovate bot force-pushed the renovate/volsync branch from f1bdba9 to 30c5c30 Compare April 4, 2024 04:06
@renovate renovate bot changed the title feat(container): update volsync group ( 0.8.0 → 0.9.0 ) feat(container): update volsync group ( 0.8.0 → 0.9.1 ) Apr 12, 2024
@renovate renovate bot force-pushed the renovate/volsync branch from 30c5c30 to 809cd69 Compare April 12, 2024 19:41
@smbonn2005 smbonn2005 merged commit 2f4ae60 into main Apr 13, 2024
1 check passed
@renovate renovate bot deleted the renovate/volsync branch April 13, 2024 04:47
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.

1 participant