deps: bump restic/restic from 0.17.1 to 0.17.2 in /config/ansible/roles/ferrarimarco_home_lab_node/files/config/restic

[dependabot]

Bumps restic/restic from 0.17.1 to 0.17.2.

Release notes

Sourced from restic/restic's releases.

restic 0.17.2

Changelog for restic 0.17.2 (2024-10-27)

The following sections list the changes in restic 0.17.2 relevant to restic users. The changes are ordered by importance.

Summary

• Fix #4004: Support container-level SAS/SAT tokens for Azure backend
• Fix #5047: Resolve potential error during concurrent cache cleanup
• Fix #5050: Return error if tag fails to lock repository
• Fix #5057: Exclude irregular files from backups
• Fix #5063: Correctly backup extended metadata when using VSS on Windows

Details

• Bugfix #4004: Support container-level SAS/SAT tokens for Azure backend

  Restic previously expected SAS/SAT tokens to be generated at the account level, which prevented tokens created at the container level from being used to initialize a repository. This caused an error when attempting to initialize a repository with container-level tokens.

  Restic now supports both account-level and container-level SAS/SAT tokens for initializing a repository.

  #4004 #5093

• Bugfix #5047: Resolve potential error during concurrent cache cleanup

  When multiple restic processes ran concurrently, they could compete to remove obsolete snapshots from the local backend cache, sometimes leading to a "no such file or directory" error. Restic now suppresses this error to prevent issues during cache cleanup.

  #5047

• Bugfix #5050: Return error if tag fails to lock repository

  Since restic 0.17.0, the tag command did not return an error when it failed to open or lock the repository. This issue has now been fixed.

  #5050 #5056

• Bugfix #5057: Exclude irregular files from backups

  Since restic 0.17.1, files with the type irregular could mistakenly be included in snapshots, especially when backing up special file types on Windows that restic cannot process. This issue has now been fixed.

  Previously, this bug caused the check command to report errors like the following one:

    tree 12345678[...]: node "example.zip" with invalid type "irregular"
  

  To repair affected snapshots, upgrade to restic 0.17.2 and run:

... (truncated)

Changelog

Sourced from restic/restic's changelog.

Changelog for restic 0.17.2 (2024-10-27)

The following sections list the changes in restic 0.17.2 relevant to restic users. The changes are ordered by importance.

Summary

• Fix #4004: Support container-level SAS/SAT tokens for Azure backend
• Fix #5047: Resolve potential error during concurrent cache cleanup
• Fix #5050: Return error if tag fails to lock repository
• Fix #5057: Exclude irregular files from backups
• Fix #5063: Correctly backup extended metadata when using VSS on Windows

Details

• Bugfix #4004: Support container-level SAS/SAT tokens for Azure backend

  Restic previously expected SAS/SAT tokens to be generated at the account level, which prevented tokens created at the container level from being used to initialize a repository. This caused an error when attempting to initialize a repository with container-level tokens.

  Restic now supports both account-level and container-level SAS/SAT tokens for initializing a repository.

  restic/restic#4004 restic/restic#5093

• Bugfix #5047: Resolve potential error during concurrent cache cleanup

  When multiple restic processes ran concurrently, they could compete to remove obsolete snapshots from the local backend cache, sometimes leading to a "no such file or directory" error. Restic now suppresses this error to prevent issues during cache cleanup.

  restic/restic#5047

• Bugfix #5050: Return error if tag fails to lock repository

  Since restic 0.17.0, the tag command did not return an error when it failed to open or lock the repository. This issue has now been fixed.

  restic/restic#5050 restic/restic#5056

• Bugfix #5057: Exclude irregular files from backups

  Since restic 0.17.1, files with the type irregular could mistakenly be included in snapshots, especially when backing up special file types on Windows that restic cannot process. This issue has now been fixed.

... (truncated)

Commits

• 2fb07dc Add version for 0.17.2
• 5dcee7f Update manpages and auto-completion
• 44968c7 Generate CHANGELOG.md for 0.17.2
• dbb5fb9 Prepare changelog for 0.17.2
• 3a4a5a8 Merge pull request #5102 from MichaelEischer/polish-changelogs
• d8d955e Tweak wording
• 2ce4850 polish changelogs
• f72febb Merge pull request #5099 from MichaelEischer/hackport-fix-vss-metadata
• ee9a5cd add vss metadata changelog
• 46dce1f backup: work around file deletion error in test
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[ferrarimarco]

@dependabot rebase