restic: baixar versions anteriors

Changelog for restic 0.19.1 (2026-07-05)
The following sections list the changes in restic 0.19.1 relevant to restic users. The changes are ordered by importance.
Summary
- Fix #5234: Prevent mounting over the repository directory
- Fix #5667: Skip inaccessible backup source paths
- Fix #5722: Update mount latest symlink after snapshot reload
- Fix #21866: Hide stats progress bar in JSON mode
- Fix #21869: Restore old behavior of snapshots --latest <n> without --group-by
- Fix #21876: Show timezone location in snapshots output
- Fix #21879: Prevent crash in mountpoint validation if mountpoint is inaccessible
- Fix #21895: Remove read-only files via the SFTP backend on Windows servers
- Fix #21899: Make backup respect excludes for duplicate directory entries
Details
- Bugfix #5234: Prevent mounting over the repository directory
Using a local repository directory as the mount target — or a path that contains it, or that it contains — caused the FUSE server to read its own backend files through the new mount, deadlocking the kernel and requiring a long reboot to recover.
Restic now resolves both paths and refuses any such overlap with a clear error before mounting.
#5234 #5348
- Bugfix #5667: Skip inaccessible backup source paths
The backup command only skipped source paths that did not exist. A path that could not be accessed for another reason, such as a malformed path on Windows, was kept and produced an empty snapshot. Restic now skips any such path and aborts if none remain.
#5667 #21852
- Bugfix #5722: Update mount latest symlink after snapshot reload
When restic mount was kept running while new snapshots were created, the new snapshots appeared in the mountpoint, but the latest symlink could still point to the previously latest snapshot. Restic now invalidates the cached snapshot directory entries after a snapshot reload so that latest points to the newest snapshot.
#5722 #21873
- Bugfix #21866: Hide stats progress bar in JSON mode
Since restic 0.19.0, the stats command shows a progress bar. This progress bar was unintentionally displayed also when using the --json option, mixing regular text output with JSON. This is now fixed.
#21866 #21871
- Bugfix #21869: Restore old behavior of snapshots --latest <n> without --group-by
Restic 0.19.0 accidentally changed the behavior of snapshots --latest <n> to no longer group snapshots by host and paths by default.
The snapshots --latest <n> command now again uses the old behavior of grouping by host and paths when --group-by is not specified. However, when specifying --group-by the output is still grouped as requested, as in restic 0.19.0.
#21869 #21875
- Bugfix #21876: Show timezone location in snapshots output
With restic 0.19.0, the snapshots command printed the current timezone when listing snapshots. However, that timezone label might change during the year, for example with daylight saving time. Restic now prints a more consistent and shorter version of the text.
#21876 https://forum.restic.net/t/possible-bug-in-timezone-naming/10867
- Bugfix #21879: Prevent crash in mountpoint validation if mountpoint is inaccessible
Since restic 0.19.0, the mount command validates a mountpoint before loading the repository. If restic was unable to stat the mountpoint, this would result in a crash. This has now been fixed to correctly return an error instead.
#21879
- Bugfix #21895: Remove read-only files via the SFTP backend on Windows servers
Since restic 0.19.0, repository files on the SFTP backend are marked read-only after save. On Windows SFTP servers, removing them failed with a permission error. The SFTP backend now clears the read-only flag before removing the file.
#21895 #21897
- Bugfix #21899: Make backup respect excludes for duplicate directory entries
Since restic 0.19.0, backing up a directory with duplicate directory entries always produced "Warning: at least one source file could not be read", even when those files were excluded. This has now been fixed.
#21899 #21900

Changelog for restic 0.19.0 (2026-06-09)
The following sections list the changes in restic 0.19.0 relevant to restic users. The changes are ordered by importance.
Summary
- Fix #2034: Support serving a restic mount of a Windows system via Samba
- Fix #4447: Use mode 0700 for repository directories created over SFTP
- Fix #4467: Exit with code 3 when some backup source paths do not exist
- Fix #4759: Error out when environment variables hold invalid values
- Fix #5233: Return exit code 3 when failing to remove snapshots
- Fix #5258: Exit with code 130 on SIGINT
- Fix #5280: Reject impossible find time bounds immediately
- Fix #5280: Make find --pack list blobs for tree packs
- Fix #5354: Allow rclone and sftp backends when running in background
- Fix #5427: Correctly restore ACL inheritance state on Windows
- Fix #5477: Password prompt was sometimes not shown for backup -v
- Fix #5487: Mark repository files read-only when using the SFTP backend
- Fix #5586: Correctly handle snapshots --group-by with --latest
- Fix #5595: Avoid spurious chmod errors on certain file backends
- Fix #5683: Prevent backup --stdin-from-command from hanging
- Fix #5757: Respect --user and --host in key passwd
- Fix #21820: Correct handling of duplicate index entries
- Fix #21820: Correctly handle pack files missing from the index
- Chg #5293: Prune small packfiles more aggressively
- Chg #5767: Prevent excluding paths explicitly passed to backup
- Chg #21791: Update dependencies and require Go 1.25 or newer
- Enh #3326: Limit check to snapshots selected by filters
- Enh #3572: Support restoring ownership by name on UNIX systems
- Enh #3738: Optional GitHub token for self-update API requests
- Enh #4278: Support include filters in the rewrite command
- Enh #4728: Support zstd compression levels fastest and better
- Enh #4868: Include repository ID in the filesystem name used by mount
- Enh #5175: Add status counters to copy in verbose text output
- Enh #5352: Support excluding cloud-backed files on macOS
- Enh #5383: Reduce progress bar refresh rates to decrease energy usage
- Enh #5424: Enable Windows filesystem privileges before file access
- Enh #5440: Make --host override environment variable RESTIC_HOST
- Enh #5448: Support configuring nice and ionice in the Docker image
- Enh #5453: Copy multiple snapshots in batches
- Enh #5523: Add Open Container Initiative labels to release Docker image
- Enh #5531: Reduce Azure storage costs by optimizing uploads
- Enh #5562: Rewrite only changed status lines each frame
- Enh #5588: Show timezone context in snapshots output
- Enh #5610: Reduce check, copy, diff and stats memory usage
- Enh #5689: Show more detailed progress for stats
- Enh #5713: Significantly speed up index loading
- Enh #5718: Stricter and earlier validation of the mount point
Details
- Bugfix #2034: Support serving a restic mount of a Windows system via Samba
A repository mounted using restic mount on a POSIX system could not use Samba to serve files from backups of Windows systems, while backups of non-Windows systems could be served successfully. This has now been fixed.
#2034 #4382 #21784
- Bugfix #4447: Use mode 0700 for repository directories created over SFTP
When creating a repository over SFTP, restic created the repository directories with the SFTP server's default permissions, often 0755, rather than the 0700 permissions it uses for local repositories.
Restic now creates these directories with 0700 permissions.
#4447 #21817
- Bugfix #4467: Exit with code 3 when some backup source paths do not exist
Restic used to exit with code 0 when a top-level backup source path was missing, and exited with code 3 only when a child path under an existing source did not exist. Scripts that relied on the exit code could therefore treat an incomplete backup as success.
Restic now exits with code 3 when any backup source path does not exist.
#4467 #5347
- Bugfix #4759: Error out when environment variables hold invalid values
If the environment var

Changelog for restic 0.18.1 (2025-09-21)
The following sections list the changes in restic 0.18.1 relevant to restic users. The changes are ordered by importance.
Summary
- Fix #5324: Correctly handle backup --stdin-filename with directory paths
- Fix #5325: Accept RESTIC_HOST environment variable in forget command
- Fix #5342: Ignore "chmod not supported" errors when writing files
- Fix #5344: Ignore EOPNOTSUPP errors for extended attributes
- Fix #5421: Fix rare crash if directory is removed during backup
- Fix #5429: Stop retrying uploads when rest-server runs out of space
- Fix #5467: Improve handling of download retries in check command
Details
- Bugfix #5324: Correctly handle backup --stdin-filename with directory paths
In restic 0.18.0, the backup command failed if a filename that includes at least a directory was passed to --stdin-filename. For example, --stdin-filename /foo/bar resulted in the following error:
Fatal: unable to save snapshot: open /foo: no such file or directory
This has now been fixed.
#5324 #5356
- Bugfix #5325: Accept RESTIC_HOST environment variable in forget command
The forget command did not use the host name from the RESTIC_HOST environment variable when filtering snapshots. This has now been fixed.
#5325 #5327
- Bugfix #5342: Ignore "chmod not supported" errors when writing files
Restic 0.18.0 introduced a bug that caused chmod xxx: operation not supported errors to appear when writing to a local file repository that did not support chmod (like CIFS or WebDAV mounted via FUSE). Restic now ignores those errors.
#5342
- Bugfix #5344: Ignore EOPNOTSUPP errors for extended attributes
Restic 0.18.0 added extended attribute support for NetBSD 10+, but not all NetBSD filesystems support extended attributes. Other BSD systems can likewise return EOPNOTSUPP, so restic now ignores these errors.
#5344
- Bugfix #5421: Fix rare crash if directory is removed during backup
In restic 0.18.0, the backup command could crash if a directory was removed between reading its metadata and listing its directory content. This has now been fixed.
#5421
- Bugfix #5429: Stop retrying uploads when rest-server runs out of space
When rest-server returns a 507 Insufficient Storage error, it indicates that no more storage capacity is available. Restic now correctly stops retrying uploads in this case.
#5429 #5452
- Bugfix #5467: Improve handling of download retries in check command
In very rare cases, the check command could unnecessarily report repository damage if the backend returned incomplete, corrupted data on the first download try which is afterwards resolved by a download retry.
This could result in an error output like the following:
Load(<data/34567890ab>, 33918928, 0) returned error, retrying after 871.35598ms: readFull: unexpected EOF
Load(<data/34567890ab>, 33918928, 0) operation successful after 1 retries
check successful on second attempt, original error pack 34567890ab[...] contains 6 errors: [blob 12345678[...]: decrypting blob <data/12345678> from 34567890 failed: ciphertext verification failed ...]
[...]
Fatal: repository contains errors
This fix only applies to a very specific case where the log shows operation successful after 1 retries followed by a check successful on second attempt, original error that only reports ciphertext verification failed errors in the pack file. If any other errors are reported in the pack file, then the repository still has to be considered as damaged.
Now, only the check result of the last download retry is reported as intended.
#5467 #5495

Changelog for restic 0.18.0 (2025-03-27)
The following sections list the changes in restic 0.18.0 relevant to restic users. The changes are ordered by importance.
Summary
- Sec #5291: Mitigate attack on content-defined chunking algorithm
- Fix #1843: Correctly restore long filepaths' timestamp on old Windows
- Fix #2165: Ignore disappeared backup source files
- Fix #5153: Include root tree when searching using find --tree
- Fix #5169: Prevent Windows VSS event log 8194 warnings for backup with fs snapshot
- Fix #5212: Fix duplicate data handling in prune --max-unused
- Fix #5249: Fix creation of oversized index by repair index --read-all-packs
- Fix #5259: Fix rare crash in command output
- Chg #4938: Update dependencies and require Go 1.23 or newer
- Chg #5162: Promote feature flags
- Enh #1378: Add JSON support to check command
- Enh #2511: Support generating shell completions to stdout
- Enh #3697: Allow excluding online-only cloud files (e.g. OneDrive)
- Enh #4179: Add sort option to ls command
- Enh #4433: Change default sort order for find output
- Enh #4521: Add support for Microsoft Blob Storage access tiers
- Enh #4942: Add snapshot summary statistics to rewritten snapshots
- Enh #4948: Format exit errors as JSON when requested
- Enh #4983: Add SLSA provenance to GHCR container images
- Enh #5054: Enable compression for ZIP archives in dump command
- Enh #5081: Add retry mechanism for loading repository config
- Enh #5089: Allow including/excluding extended file attributes during restore
- Enh #5092: Show count of deleted files and directories during restore
- Enh #5109: Make small pack size configurable for prune
- Enh #5119: Add start and end timestamps to backup JSON output
- Enh #5131: Add DragonFlyBSD support
- Enh #5137: Make tag command print which snapshots were modified
- Enh #5141: Provide clear error message if AZURE_ACCOUNT_NAME is not set
- Enh #5173: Add experimental S3 cold storage support
- Enh #5174: Add xattr support for NetBSD 10+
- Enh #5251: Improve retry handling for flaky rclone backends
- Enh #52897: Make recover automatically rebuild index when needed
Details
- Security #5291: Mitigate attack on content-defined chunking algorithm
Restic uses Rabin Fingerprints for its content-defined chunker. The algorithm relies on a secret polynomial to split files into chunks.
As shown in the paper "Chunking Attacks on File Backup Services using Content-Defined Chunking" by Boris Alexeev, Colin Percival and Yan X Zhang, an attacker that can observe chunk sizes for a known file can derive the secret polynomial. Knowledge of the polynomial might in some cases allow an attacker to check whether certain large files are stored in a repository.
A practical attack is nevertheless hard as restic merges multiple chunks into opaque pack files and by default processes multiple files in parallel. This likely prevents an attacker from matching pack files to the attacker-known file and thereby prevents the attack.
Despite the low chances of a practical attack, restic now has added mitigation that randomizes how chunks are assembled into pack files. This prevents attackers from guessing which chunks are part of a pack file and thereby prevents learning the chunk sizes.
#5291 #5295
- Bugfix #1843: Correctly restore long filepaths' timestamp on old Windows
The restore command now correctly restores timestamps for files with paths longer than 256 characters on Windows versions prior to Windows 10 1607.
#1843 #5061
- Bugfix #2165: Ignore disappeared backup source files
The backup command now quietly skips files that are removed between directory listing and backup, instead of printing errors like:
error: lstat /some/file/name: no such file or directory
#2165 #3098 #5143 #5145
- Bugfix #5153: Include root tree when searching using find --tree
The restic find --tree command did not find trees referenced by restic snapshot --json. It now correctly includes the root tree when searching.
#5153
- Bugfix #5169: Prevent Windows VSS e

Changelog for restic 0.17.3 (2024-11-08)
The following sections list the changes in restic 0.17.3 relevant to restic users. The changes are ordered by importance.Summary
- Fix #4971: Fix unusable mount on macOS Sonoma
- Fix #5003: Fix metadata errors during backup of removable disks on Windows
- Fix #5101: Do not retry load/list operation if SFTP connection is broken
- Fix #5107: Fix metadata error on Windows for backups using VSS
- Enh #5096: Allow prune --dry-run without lock
Details
- Bugfix #4971: Fix unusable mount on macOS SonomaOn macOS Sonoma when using FUSE-T, it was not possible to access files in a mounted repository. This issue is now resolved.#4971 #5048
- Bugfix #5003: Fix metadata errors during backup of removable disks on WindowsSince restic 0.17.0, backing up removable disks on Windows could report errors with retrieving metadata like shown below.
error: incomplete metadata for d:\filename: get named security info failed with: Access is denied.

This has now been fixed.#5003 #5123 https://forum.restic.net/t/backing-up-a-folder-from-a-veracrypt-volume-brings-up-errors-since-restic-v17-0/8444
- Bugfix #5101: Do not retry load/list operation if SFTP connection is brokenWhen using restic with the SFTP backend, backend operations that load a file or list files were retried even if the SFTP connection was broken. This has now been fixed.#5101 https://forum.restic.net/t/restic-hanging-on-backup/8559
- Bugfix #5107: Fix metadata error on Windows for backups using VSSSince restic 0.17.2, when creating a backup on Windows using --use-fs-snapshot, restic would report an error like the following:
error: incomplete metadata for C:\: get EA failed while opening file handle for path \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopyXX\, with: The process cannot access the file because it is being used by another process.

This has now been fixed by correctly handling paths that refer to volume shadow copy snapshots.#5107 #5110 #5112
- Enhancement #5096: Allow prune --dry-run without lockThe prune --dry-run --no-lock now allows performing a dry-run without locking the repository. Note that if the repository is modified concurrently, prune may return inaccurate statistics or errors.#5096

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 backendRestic 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 cleanupWhen 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 repositorySince 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 backupsSince 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:
restic repair snapshots --forget

This will remove the irregular files from the snapshots (creating a new snapshot ID for each of the affected snapshots).#5057 https://forum.restic.net/t/errors-found-by-check-1-invalid-type-irregular-2-ciphertext-verification-failed/8447/2
- Bugfix #5063: Correctly backup extended metadata when using VSS on WindowsOn Windows, when creating a backup with the --use-fs-snapshot option, restic read extended metadata from the original filesystem path instead of from the snapshot. This could result in errors if files were removed during the backup process.This issue has now been resolved.#5063 #5097 #5099

Changelog for restic 0.17.1 (2024-09-05)
The following sections list the changes in restic 0.17.1 relevant to restic users. The changes are ordered by importance.Summary
- Fix #2004: Correctly handle volume names in backup command on Windows
- Fix #4945: Include missing backup error text with --json
- Fix #4953: Correctly handle long paths on older Windows versions
- Fix #4957: Fix delayed cancellation of certain commands
- Fix #4958: Don't ignore metadata-setting errors during restore
- Fix #4969: Correctly restore timestamp for files with resource forks on macOS
- Fix #4975: Prevent backup --stdin-from-command from panicking
- Fix #4980: Skip extended attribute processing on unsupported Windows volumes
- Fix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error
- Fix #5005: Fix rare failures to retry locking a repository
- Fix #5018: Improve HTTP/2 support for REST backend
- Chg #4953: Also back up files with incomplete metadata
- Enh #4795: Display progress bar for restore --verify
- Enh #4934: Automatically clear removed snapshots from cache
- Enh #4944: Print JSON-formatted errors during restore --json
- Enh #4959: Return exit code 12 for "bad password" errors
- Enh #4970: Make timeout for stuck requests customizable
Details
- Bugfix #2004: Correctly handle volume names in backup command on WindowsOn Windows, when the specified backup target only included the volume name without a trailing slash, for example, C:, then restoring the resulting snapshot would result in an error. Note that using C:\ as backup target worked correctly.Specifying volume names is now handled correctly. To restore snapshots created before this bugfix, use the : syntax. For example, to restore a snapshot with ID 12345678 that backed up C:, use the following command:
restic restore 12345678:/C/C:./ --target output/folder

#2004 #5028
- Bugfix #4945: Include missing backup error text with --jsonPreviously, when running a backup with the --json option, restic failed to include the actual error message in the output, resulting in "error": {} being displayed.This has now been fixed, and restic now includes the error text in JSON output.#4945 #4946
- Bugfix #4953: Correctly handle long paths on older Windows versionsOn older Windows versions, like Windows Server 2012, restic 0.17.0 failed to back up files with long paths. This problem has now been resolved.#4953 #4954
- Bugfix #4957: Fix delayed cancellation of certain commandsSince restic 0.17.0, some commands did not immediately respond to cancellation via Ctrl-C (SIGINT) and continued running for a short period. The most affected commands were diff,find, ls, stats and rewrite. This is now resolved.#4957 #4960
- Bugfix #4958: Don't ignore metadata-setting errors during restorePreviously, restic used to ignore errors when setting timestamps, attributes, or file modes during a restore. It now reports those errors, except for permission related errors when running without root privileges.#4958
- Bugfix #4969: Correctly restore timestamp for files with resource forks on macOSOn macOS, timestamps were not restored for files with resource forks. This has now been fixed.#4969 #5006
- Bugfix #4975: Prevent backup --stdin-from-command from panickingRestic would previously crash if --stdin-from-command was specified without providing a command. This issue has now been fixed.#4975 #4976
- Bugfix #4980: Skip extended attribute processing on unsupported Windows volumesWith restic 0.17.0, backups of certain Windows paths, such as network drives, failed due to errors while fetching extended attributes.Restic now skips extended attribute processing for volumes where they are not supported.#4955 #4950 #4980 #4998
- Bugfix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" errorOn Windows, creating a backup could sometimes trigger the following error:
error: nodeFromFileInfo [...]: get named security info failed with: a required privilege is not held by the client.

This has now be

- Fix #2565: Support "unlimited" in forget --keep-* options
- Fix #3311: Support non-UTF8 paths as symlink target
- Fix #4199: Avoid lock refresh issues on slow network connections
- Fix #4274: Improve lock refresh handling after standby
- Fix #4319: Correctly clean up status bar output of the backup command
- Fix #4333: generate and init no longer silently ignore unexpected arguments
- Fix #4400: Ignore missing folders in rest backend
- Chg #4176: Fix JSON message type of scan_finished for the backup command
- Chg #4201: Require Go 1.20 for Solaris builds
- Enh #426: Show progress bar during restore
- Enh #719: Add --retry-lock option
- Enh #1495: Sort snapshots by timestamp in restic find
- Enh #1759: Add repair index and repair snapshots commands
- Enh #1926: Allow certificate paths to be passed through environment variables
- Enh #2359: Provide multi-platform Docker images
- Enh #2468: Add support for non-global Azure clouds
- Enh #2679: Reduce file fragmentation for local backend
- Enh #3328: Reduce memory usage by up to 25%
- Enh #3397: Improve accuracy of ETA displayed during backup
- Enh #3624: Keep oldest snapshot when there are not enough snapshots
- Enh #3698: Add support for Managed / Workload Identity to azure backend
- Enh #3871: Support <snapshot>:<subfolder> syntax to select subfolders
- Enh #3941: Support --group-by for backup parent selection
- Enh #4130: Cancel current command if cache becomes unusable
- Enh #4159: Add --human-readable option to ls and find commands
- Enh #4188: Include restic version in snapshot metadata
- Enh #4220: Add jq binary to Docker image
- Enh #4226: Allow specifying region of new buckets in the gs backend
- Enh #4375: Add support for extended attributes on symlinks
- Bugfix #2565: Support "unlimited" in forget --keep-* options
2565 #4234
- Bugfix #3311: Support non-UTF8 paths as symlink target
3311 #3802
- Bugfix #4199: Avoid lock refresh issues on slow network connections
4199 #4304
- Bugfix #4274: Improve lock refresh handling after standby
4274 #4374
- Bugfix #4319: Correctly clean up status bar output of the backup command
4319 #4318
- Bugfix #4333: generate and init no longer silently ignore unexpected arguments
4333
- Bugfix #4400: Ignore missing folders in rest backend
235 #4400
- Change #4176: Fix JSON message type of scan_finished for the backup command
4176
- Change #4201: Require Go 1.20 for Solaris builds
4201
- Enhancement #426: Show progress bar during restore
426 #3413 #3627 #3991 #4314 https://forum.restic.net/t/progress-bar-for-restore/5210
- Enhancement #719: Add --retry-lock option
719 #2214 #4107
- Enhancement #1495: Sort snapshots by timestamp in restic find
1495 #4409
- Enhancement #1759: Add repair index and repair snapshots commands
1759 #1714 #1798 #2334 #2876 https://forum.restic.net/t/corrupted-repo-how-to-repair/799https://forum.restic.net/t/recovery-options-for-damaged-repositories/1571
- Enhancement #1926: Allow certificate paths to be passed through environment variables
1926 #4384
- Enhancement #2359: Provide multi-platform Docker images
2359 #4269 #4364
- Enhancement #2468: Add support for non-global Azure clouds
2468 #4387
- Enhancement #2679: Reduce file fragmentation for local backend
2679 #3261
- Enhancement #3328: Reduce memory usage by up to 25%
3328 #4352 #4353
- Enhancement #3397: Improve accuracy of ETA displayed during backup
3397 #3563
- Enhancement #3624: Keep oldest snapshot when there are not enough snapshots
3624 #4366 https://forum.restic.net/t/keeping-yearly-snapshots-policy-when-backup-began-during-the-year/4670/2
- Enhancement #3698: Add support for Managed / Workload Identity to azure backend
3698 #4029
- Enhancement #3871: Support <snapshot>:<subfolder> syntax to select subfolders
3871 #4334
- Enhancement #3941: Support --group-by for backup parent selection
3941 #4081
- Enhancement #4130: Cancel current command if cache becomes unusable
4130 #4166
- Enhancement #4159: Add --human-readable option to ls and find commands
4159 #4

- Sec #4275:
Update golang.org/x/net to address CVE-2022-41723
- Fix #2260:
Sanitize filenames printed by backup during processing
- Fix #4211:
Make dump interpret --host and --path correctly
- Fix #4239:
Correct number of blocks reported in mount point
- Fix #4253:
Minimize risk of spurious filesystem loops with mount
- Enh #4180:
Add release binaries for riscv64 architecture on Linux
- Enh #4219:
Upgrade Minio to version 7.0.49
- Security #4275:
Update golang.org/x/net to address CVE-2022-41723
4275 #4213
- Bugfix #2260:
Sanitize filenames printed by backup during processing
2260 #4191 #4192
- Bugfix #4211:
Make dump interpret --host and --path correctly
4211 #4212
- Bugfix #4239:
Correct number of blocks reported in mount point
4239 #4240
- Bugfix #4253:
Minimize risk of spurious filesystem loops with mount
4253 #4255
- Enhancement #4180:
Add release binaries for riscv64 architecture on Linux
4180
- Enhancement #4219:
Upgrade Minio to version 7.0.49

We're very pleased to present you restic 0.15.1! This is just a small bugfix release, fixing some issues that arose after 0.15.0 was published.