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

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 command to report errors like the following one: