Merge branch 'patch-release'

changelog/unreleased/issue-4004

@@ -1,12 +0,0 @@
-Bugfix: Allow use of container level SAS/SAT tokens with Azure backend
-
-When using a SAS/SAT token for authentication with Azure, restic was expecting
-the provided token to be generated at the account level, granting permissions
-to the storage account and all its containers. This caused an error that did
-not allow tokens that were generated at the container level to be used to 
-initalize a repository.
-Restic now allows SAS/SAT tokens that were generated at the account or 
-container level to be used to initalize a repository.
-
-https://github.com/restic/restic/issues/4004
-https://github.com/restic/restic/pull/5093

changelog/unreleased/issue-5050

@@ -1,7 +0,0 @@
-Bugfix: Missing error if `tag` fails to lock repository
-
-Since restic 0.17.0, the `tag` command did not return an error if it failed to
-open or lock the repository. This has been fixed.
-
-https://github.com/restic/restic/issues/5050
-https://github.com/restic/restic/pull/5056

changelog/unreleased/issue-5063

@@ -1,10 +0,0 @@
-Bugfix: Correctly `backup` extended metadata when using VSS on Windows
-
-On Windows, when creating a backup using the `--use-fs-snapshot` option,
-then the extended metadata was not read from the filesystem snapshot. This
-could result in errors when files have been removed in the meantime.
-
-This issue has been resolved.
-
-https://github.com/restic/restic/issues/5063
-https://github.com/restic/restic/pull/5097

changelog/unreleased/pull-5047

@@ -1,7 +0,0 @@
-Bugfix: Fix possible error on concurrent cache cleanup
-
-Fix for multiple restic processes executing concurrently and racing to
-remove obsolete snapshots from the local backend cache.  Restic now suppresses the `no
-such file or directory` error.
-
-https://github.com/restic/restic/pull/5047

changelog/unreleased/pull-5057

@@ -1,21 +0,0 @@
-Bugfix: Do not include irregular files in backup
-
-Since restic 0.17.1, files with type `irregular` could incorrectly be included
-in snapshots. This is most likely to occur when backing up special file types
-on Windows that cannot be handled by restic.
-
-This has been fixed.
-
-When running the `check` command this bug resulted in an error like the
-following:
-
-```
-  tree 12345678[...]: node "example.zip" with invalid type "irregular"
-```
-
-Repairing the affected snapshots requires upgrading to restic 0.17.2 and then
-manually running `restic repair snapshots --forget`. This will remove the
-`irregular` files from the snapshots.
-
-https://github.com/restic/restic/pull/5057
-https://forum.restic.net/t/errors-found-by-check-1-invalid-type-irregular-2-ciphertext-verification-failed/8447/2