restic version history

- Prevent mounting over repository directory to avoid deadlocks - Skip inaccessible backup paths and respect excludes for duplicates - Fix mount command issues with latest symlink and validation - Various fixes for snapshots, stats, and SFTP backend behavior

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](https://github.com/restic/restic/issues/2034): Support serving a `restic mount` of a Windows system via Samba * Fix [#4447](https://github.com/restic/restic/issues/4447): Use mode 0700 for repository directories created over SFTP * Fix [#4467](https://github.com/restic/restic/issues/4467): Exit with code 3 when some `backup` source paths do not exist * Fix [#4759](https://github.com/restic/restic/issues/4759): Error out when environment variables hold invalid values * Fix [#5233](https://github.com/restic/restic/issues/5233): Return exit code 3 when failing to remove snapshots * Fix [#5258](https://github.com/restic/restic/issues/5258): Exit with code 130 on SIGINT * Fix [#5280](https://github.com/restic/restic/issues/5280): Reject impossible `find` time bounds immediately * Fix [#5280](https://github.com/restic/restic/issues/5280): Make `find --pack` list blobs for tree packs * Fix [#5354](https://github.com/restic/restic/is

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](https://github.com/restic/restic/issues/5324): Correctly handle `backup --stdin-filename` with directory paths * Fix [#5325](https://github.com/restic/restic/issues/5325): Accept `RESTIC_HOST` environment variable in `forget` command * Fix [#5342](https://github.com/restic/restic/issues/5342): Ignore "chmod not supported" errors when writing files * Fix [#5344](https://github.com/restic/restic/issues/5344): Ignore `EOPNOTSUPP` errors for extended attributes * Fix [#5421](https://github.com/restic/restic/pull/5421): Fix rare crash if directory is removed during backup * Fix [#5429](https://github.com/restic/restic/issues/5429): Stop retrying uploads when rest-server runs out of space * Fix [#5467](https://github.com/restic/restic/issues/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 `b

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](https://github.com/restic/restic/issues/5291): Mitigate attack on content-defined chunking algorithm * Fix [#1843](https://github.com/restic/restic/issues/1843): Correctly restore long filepaths' timestamp on old Windows * Fix [#2165](https://github.com/restic/restic/issues/2165): Ignore disappeared backup source files * Fix [#5153](https://github.com/restic/restic/pull/5153): Include root tree when searching using `find --tree` * Fix [#5169](https://github.com/restic/restic/issues/5169): Prevent Windows VSS event log 8194 warnings for backup with fs snapshot * Fix [#5212](https://github.com/restic/restic/pull/5212): Fix duplicate data handling in `prune --max-unused` * Fix [#5249](https://github.com/restic/restic/pull/5249): Fix creation of oversized index by `repair index --read-all-packs` * Fix [#5259](https://github.com/restic/restic/issues/5259): Fix rare crash in command output * Chg [#4938](https://github.com/restic/re

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](https://github.com/restic/restic/issues/4971): Fix unusable `mount` on macOS Sonoma * Fix [#5003](https://github.com/restic/restic/issues/5003): Fix metadata errors during backup of removable disks on Windows * Fix [#5101](https://github.com/restic/restic/pull/5101): Do not retry load/list operation if SFTP connection is broken * Fix [#5107](https://github.com/restic/restic/issues/5107): Fix metadata error on Windows for backups using VSS * Enh [#5096](https://github.com/restic/restic/pull/5096): Allow `prune --dry-run` without lock Details ------- * Bugfix #4971: Fix unusable `mount` on macOS Sonoma On macOS Sonoma when using FUSE-T, it was not possible to access files in a mounted repository. This issue is now resolved. [#4971](https://github.com/restic/restic/issues/4971) [#5048](https://github.com/restic/restic/pull/5048) * Bugfix #5003: Fix metadata errors during backup of removable disks on Windows

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](https://github.com/restic/restic/issues/4004): Support container-level SAS/SAT tokens for Azure backend * Fix [#5047](https://github.com/restic/restic/pull/5047): Resolve potential error during concurrent cache cleanup * Fix [#5050](https://github.com/restic/restic/issues/5050): Return error if `tag` fails to lock repository * Fix [#5057](https://github.com/restic/restic/pull/5057): Exclude irregular files from backups * Fix [#5063](https://github.com/restic/restic/issues/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

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](https://github.com/restic/restic/issues/2004): Correctly handle volume names in `backup` command on Windows * Fix [#4945](https://github.com/restic/restic/issues/4945): Include missing backup error text with `--json` * Fix [#4953](https://github.com/restic/restic/issues/4953): Correctly handle long paths on older Windows versions * Fix [#4957](https://github.com/restic/restic/issues/4957): Fix delayed cancellation of certain commands * Fix [#4958](https://github.com/restic/restic/pull/4958): Don't ignore metadata-setting errors during restore * Fix [#4969](https://github.com/restic/restic/issues/4969): Correctly restore timestamp for files with resource forks on macOS * Fix [#4975](https://github.com/restic/restic/issues/4975): Prevent `backup --stdin-from-command` from panicking * Fix [#4980](https://github.com/restic/restic/pull/4980): Skip extended attribute processing on unsupported Windows volumes * Fix [#5004](https://g

Changelog for restic 0.17.0 (2024-07-26) ======================================= The following sections list the changes in restic 0.17.0 relevant to restic users. The changes are ordered by importance. Summary ------- * Fix [#3600](https://github.com/restic/restic/issues/3600): Handle unreadable xattrs in folders above `backup` source * Fix [#4209](https://github.com/restic/restic/issues/4209): Fix slow SFTP upload performance * Fix [#4503](https://github.com/restic/restic/pull/4503): Correct hardlink handling in `stats` command * Fix [#4568](https://github.com/restic/restic/pull/4568): Prevent `forget --keep-tags <invalid>` from deleting all snapshots * Fix [#4615](https://github.com/restic/restic/pull/4615): Make `find` not sometimes ignore directories * Fix [#4656](https://github.com/restic/restic/issues/4656): Properly report ID of newly added keys * Fix [#4703](https://github.com/restic/restic/pull/4703): Shutdown cleanly when receiving SIGTERM * Fix [#4709](https://github.com/restic/restic/pull/4709): Correct `--no-lock` handling of `ls` and `tag` commands * Fix [#4760](https://github.com/restic/restic/issues/4760): Fix possible error on concurren

Changelog for restic 0.16.5 (2024-07-01) ======================================= The following sections list the changes in restic 0.16.5 relevant to restic users. The changes are ordered by importance. Summary ------- * Enh [#4799](https://github.com/restic/restic/pull/4799): Add option to force use of Azure CLI credential * Enh [#4873](https://github.com/restic/restic/issues/4873): Update dependencies Details ------- * Enhancement #4799: Add option to force use of Azure CLI credential A new environment variable `AZURE_FORCE_CLI_CREDENTIAL=true` allows forcing the use of Azure CLI credential, ignoring other credentials like managed identity. [#4799](https://github.com/restic/restic/pull/4799) * Enhancement #4873: Update dependencies A few potentially vulnerable dependencies were updated. [#4873](https://github.com/restic/restic/issues/4873) [#4878](https://github.com/restic/restic/pull/4878)

This release works around and improves detection of a bug in the compression library used by restic. The resulting issue only happens when using restic 0.16.3 and the `max` compression level (the default `auto` and `off` compression levels are not affected), and when the source files being backed up have specific data in them to trigger the bug. If you use `max` compression, you can use `restic check --read-data` to make sure you're not affected. restic is distributed as a standalone binary: download the correct file for your operating system and architecture, extract the file and just run it. If you run into any issues, please report them at [the GitHub issue tracker](https://github.com/restic/restic/issues/new) or visit [the forum](https://forum.restic.net). If you already have restic >= 0.9.4, you can use `restic self-update` to get the latest version in a secure way. The binaries released with each restic version are [reproducible](https://reproducible-builds.org/), which means that you can reproduce a byte identical version from the source code for that release. Instructions on how to do that in the [Developer Documentation](https://github.com/restic/restic/blob/master/d