restic 0.15.0 → 0.17.1
10 releases · 3 breaking changes · 6 security fixes · 0 advisories fixed
6security3breaking4deprecated63feature77fix
Breaking changes
- breaking Bugfix #4540: Restore ARMv5 support for ARM binaries The official release binaries for restic 0.16.1 were accidentally built to require ARMv7. The build process is now updated to restore support for ARMv5. Please note that restic 0.17.0 will drop support for ARMv5 and require at least ARMv6. in 0.16.2
- breaking Enhancement #4130: Cancel current command if cache becomes unusable If the cache directory was removed or ran out of space while restic was running, this would previously cause further caching attempts to fail and thereby drastically slow down the command execution. Now, the currently running… in 0.16.0
- breaking Bugfix #3750: Remove b2_download_file_by_name: 404 warning from B2 backend In some cases the B2 backend could print b2_download_file_by_name: 404: : b2.b2err warnings. These are only debug messages and can be safely ignored. Restic now uses an updated library for accessing B2, which removes the… in 0.15.1
Security changes
- security Bugfix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error On 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 been fixed. in 0.17.1
- security Enhancement #1786: Support repositories with empty password Restic previously required a password to create or operate on repositories. Using the new option --insecure-no-password it is now possible to disable this requirement. Restic will not prompt for a password when using this option. For… in 0.17.0
- security Enhancement #4873: Update dependencies A few potentially vulnerable dependencies were updated. in 0.16.5
- security Enhancement #4375: Add support for extended attributes on symlinks Restic now supports extended attributes on symlinks when backing up, restoring, or FUSE-mounting snapshots. This includes, for example, the security.selinux xattr on Linux distributions that use SELinux. in 0.16.0
- security Sec: Update golang.org/x/net to address CVE-2022-41723 in 0.15.2
- security Security #4275: Update golang.org/x/net to address CVE-2022-41723 in 0.15.2
Deprecations
- deprecated Chg: Deprecate legacy index format and s3legacy repository layout in 0.17.0
- deprecated Change #4602: Deprecate legacy index format and s3legacy repository layout Support for the legacy index format used by restic before version 0.2.0 has been deprecated and will be removed in the next minor restic version. You can use restic repair index to update the index to the current format. It… in 0.17.0
- deprecated Enhancement #4664: Make ls use message_type field in JSON output The ls command was the only restic command that used the struct_type field in its JSON output format to specify the message type. The JSON output of the ls command now also includes the message_type field, which is consistent with… in 0.17.0
- deprecated Enhancement #1759: Add repair index and repair snapshots commands The rebuild-index command has been renamed to repair index. The old name will still work, but is deprecated. When a snapshot was damaged, the only option up to now was to completely forget the snapshot, even if only some unimportant… in 0.16.0
Every release in between
fixFix: Correctly handle volume names in backup command on Windows
fixFix: Include missing backup error text with --json
fixFix: Correctly handle long paths on older Windows versions
fixFix: Fix delayed cancellation of certain commands
fixFix: Don't ignore metadata-setting errors during restore
fixFix: Correctly restore timestamp for files with resource forks on macOS
fixFix: Prevent backup --stdin-from-command from panicking
fixFix: Skip extended attribute processing on unsupported Windows volumes
fixFix: Fix spurious "A Required Privilege Is Not Held by the Client" error
fixFix: Fix rare failures to retry locking a repository
fixFix: Improve HTTP/2 support for REST backend
otherChg: Also back up files with incomplete metadata
otherEnh: Display progress bar for restore --verify
otherEnh: Automatically clear removed snapshots from cache
otherEnh: Print JSON-formatted errors during restore --json
otherEnh: Return exit code 12 for "bad password" errors
otherEnh: Make timeout for stuck requests customizable
fixBugfix #2004: Correctly handle volume names in backup command on Windows On 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…
fixBugfix #4945: Include missing backup error text with --json Previously, 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…
fixBugfix #4953: Correctly handle long paths on older Windows versions On 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.
fixBugfix #4957: Fix delayed cancellation of certain commands Since 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.
fixBugfix #4958: Don't ignore metadata-setting errors during restore Previously, 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.
fixBugfix #4969: Correctly restore timestamp for files with resource forks on macOS On macOS, timestamps were not restored for files with resource forks. This has now been fixed.
fixBugfix #4975: Prevent backup --stdin-from-command from panicking Restic would previously crash if --stdin-from-command was specified without providing a command. This issue has now been fixed.
fixBugfix #4980: Skip extended attribute processing on unsupported Windows volumes With 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…
securityBugfix #5004: Fix spurious "A Required Privilege Is Not Held by the Client" error On 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 been fixed.
fixBugfix #5005: Fix rare failures to retry locking a repository Restic 0.17.0 could in rare cases fail to retry locking a repository if one of the lock files failed to load, resulting in the error: unable to create lock in backend: circuit breaker open for file This issue has now been addressed. The…
fixBugfix #5018: Improve HTTP/2 support for REST backend If rest-server tried to gracefully shut down an HTTP/2 connection still in use by the client, it could result in the following error: http2: Transport: cannot retry err [http2: Transport received Server's graceful shutdown GOAWAY] after…
otherChange #4953: Also back up files with incomplete metadata If restic failed to read extended metadata for a file or folder during a backup, then the file or folder was not included in the resulting snapshot. Instead, a warning message was printed along with returning exit code 3 once the backup was…
otherEnhancement #4795: Display progress bar for restore --verify When the restore command is run with --verify, it now displays a progress bar while the verification step is running. The progress bar is not shown when the --json flag is specified.
otherEnhancement #4934: Automatically clear removed snapshots from cache Previously, restic only removed snapshots from the cache on the host where the forget command was executed. On other hosts that use the same repository, the old snapshots remained in the cache. Restic now automatically clears old…
otherEnhancement #4944: Print JSON-formatted errors during restore --json Restic used to print any restore errors directly to the console as freeform text messages, even when using the --json option. Now, when --json is specified, restic prints them as JSON formatted messages.
otherEnhancement #4959: Return exit code 12 for "bad password" errors Restic now returns exit code 12 when it cannot open the repository due to an incorrect password.
otherEnhancement #4970: Make timeout for stuck requests customizable Restic monitors connections to the backend to detect stuck requests. If a request does not return any data within five minutes, restic assumes the request is stuck and retries it. However, for large repositories this timeout might be…
fixFix: Handle unreadable xattrs in folders above backup source
fixFix: Fix slow SFTP upload performance
fixFix: Correct hardlink handling in stats command
deprecatedChg: Deprecate legacy index format and s3legacy repository layout
featureEnh: Add bitrot detection to diff command
featureEnh: Add --delete option to restore command
featureEnh: Add extended options to configure Windows Shadow Copy Service
featureEnh: Add support for FUSE-T with mount on macOS
featureEnh: Add --json option to version command
featureEnh: Add --ncdu option to ls command
featureEnh: Add support for feature flags
featureEnh: Add --target option to the dump command
featureEnh: Allow specifying --host via environment variable
featureEnh: Allow specifying custom User-Agent for outgoing requests
featureEnh: Add restore options to read include/exclude patterns from files
featureEnh: Add dry-run support to restore command
featureChange #4540: Require at least ARMv6 for ARM binaries The official release binaries of restic now require at least ARMv6 support for ARM platforms.
deprecatedChange #4602: Deprecate legacy index format and s3legacy repository layout Support for the legacy index format used by restic before version 0.2.0 has been deprecated and will be removed in the next minor restic version. You can use restic repair index to update the index to the current format. It…
featureChange #4627: Redesign backend error handling to improve reliability Restic now downloads pack files in large chunks instead of using a streaming download. This prevents failures due to interrupted streams. The restore command now also retries downloading individual blobs that could not be…
featureChange #4707: Disable S3 anonymous authentication by default When using the S3 backend with anonymous authentication, it continuously tried to retrieve new authentication credentials, causing bad performance. Now, to use anonymous authentication, it is necessary to pass the extended option -o…
featureEnhancement #662: Optionally skip snapshot creation if nothing changed The backup command always created a snapshot even if nothing in the backup set changed compared to the parent snapshot. Restic now supports the --skip-if-unchanged option for the backup command, which omits creating a snapshot…
featureEnhancement #805: Add bitrot detection to diff command The output of the diff command now includes the modifier ? for files to indicate bitrot in backed up files. The ? will appear whenever there is a difference in content while the metadata is exactly the same. Since files with unchanged metadata…
securityEnhancement #1786: Support repositories with empty password Restic previously required a password to create or operate on repositories. Using the new option --insecure-no-password it is now possible to disable this requirement. Restic will not prompt for a password when using this option. For…
featureEnhancement #2348: Add --delete option to restore command The restore command now supports a --delete option that allows removing files and directories from the target directory that do not exist in the snapshot. This option also allows files in the snapshot to replace non-empty directories having…
featureEnhancement #3067: Add extended options to configure Windows Shadow Copy Service Previous, restic always used a 120 seconds timeout and unconditionally created VSS snapshots for all volume mount points on disk. This behavior can now be fine-tuned by the following new extended options (available…
featureEnhancement #4048: Add support for FUSE-T with mount on macOS The restic mount command now supports creating FUSE mounts using FUSE-T on macOS.
featureEnhancement #4287: Support connection to rest-server using unix socket Restic now supports using a unix socket to connect to a rest-server version 0.13.0 or later. This allows running restic as follows: rest-server --listen unix:/tmp/rest.socket --data /path/to/data & restic -r…
featureEnhancement #4472: Support AWS Assume Role for S3 backend Previously only credentials discovered via the Minio discovery methods were used to authenticate. However, there are many circumstances where the discovered credentials have lower permissions and need to assume a specific role. This is now…
featureEnhancement #4547: Add --json option to version command Restic now supports outputting restic version along with the Go version, OS and architecture used to build restic in JSON format using version --json.
featureEnhancement #4549: Add --ncdu option to ls command NCDU (NCurses Disk Usage) is a tool to analyse disk usage of directories. It has an option to save a directory tree and analyse it later. The ls command now supports outputting snapshot information in the NCDU format using the --ncdu option.…
featureEnhancement #4573: Support rewriting host and time metadata in snapshots The rewrite command now supports rewriting the host and/or time metadata of a snapshot using the new --new-host and --new-time options.
featureEnhancement #4601: Add support for feature flags Restic now supports feature flags that can be used to enable and disable experimental features. The flags can be set using the environment variable RESTIC_FEATURES. To get a list of currently supported feature flags, use the features command.
deprecatedEnhancement #4664: Make ls use message_type field in JSON output The ls command was the only restic command that used the struct_type field in its JSON output format to specify the message type. The JSON output of the ls command now also includes the message_type field, which is consistent with…
featureEnhancement #4676: Make key command's actions separate sub-commands Each of the add, list, remove and passwd actions provided by the key command is now a separate sub-command and have its own documentation which can be invoked using restic key --help.
featureEnhancement #4678: Add --target option to the dump command Restic dump always printed to the standard output. It now supports specifying a --target file to write its output to.
featureEnhancement #4733: Allow specifying --host via environment variable Restic commands that operate on snapshots, such as restic backup and restic snapshots, support the --host option to specify the hostname for grouping snapshots. Such commands now also support specifying the hostname via the…
featureEnhancement #4764: Support forgetting all snapshots The forget command now supports the --unsafe-allow-remove-all option, which removes all snapshots in the repository. This option must always be combined with a snapshot filter (by host, path or tag). For example, the command forget --tag example…
featureEnhancement #4768: Allow specifying custom User-Agent for outgoing requests Restic now supports setting a custom User-Agent for outgoing HTTP requests using the global option --http-user-agent or the RESTIC_HTTP_USER_AGENT environment variable.
featureEnhancement #4781: Add restore options to read include/exclude patterns from files Restic now supports reading include and exclude patterns from files using the --include-file, --exclude-file, --iinclude-file and --iexclude-file options of the restore command.
featureEnhancement #4839: Add dry-run support to restore command The restore command now supports the --dry-run option to perform a dry run. Pass the --verbose=2 option to see which files would remain unchanged, and which would be updated or freshly restored.
+78 more items in the release notesfeatureEnh: Add option to force use of Azure CLI credential
otherEnh: Update dependencies
featureEnhancement #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.
securityEnhancement #4873: Update dependencies A few potentially vulnerable dependencies were updated.
fixFix: Downgrade zstd library to fix rare data corruption at max. compression
featureEnh: Add extra verification of data integrity before upload
fixBugfix #4677: Downgrade zstd library to fix rare data corruption at max. compression In restic 0.16.3, backups where the compression level was set to max (using --compression max) could in rare and very specific circumstances result in data corruption due to a bug in the library used for…
fixEnhancement #4529: Add extra verification of data integrity before upload Hardware issues, or a bug in restic or its dependencies, could previously cause corruption in the files restic created and stored in the repository. Detecting such corruption previously required explicitly running the check…
fixFix: Improve errors for irregular files on Windows
fixFix: Support backup of deduplicated files on Windows again
fixFix: Improve error handling for rclone backend
fixFix: Correct restore progress information if an error occurs
fixFix: Improve reliability of restoring large files
fixBugfix #4560: Improve errors for irregular files on Windows Since Go 1.21, most filesystem reparse points on Windows are considered to be irregular files. This caused restic to show an error: invalid node type "" error message for those files. This error message has now been improved and includes…
fixBugfix #4574: Support backup of deduplicated files on Windows again With the official release builds of restic 0.16.1 and 0.16.2, it was not possible to back up files that were deduplicated by the corresponding Windows Server feature. This also applied to restic versions built using Go…
fixBugfix #4612: Improve error handling for rclone backend Since restic 0.16.0, if rclone encountered an error while listing files, this could in rare circumstances cause restic to assume that there are no files. Although unlikely, this situation could result in data loss if it were to happen right…
fixBugfix #4624: Correct restore progress information if an error occurs If an error occurred while restoring a snapshot, this could cause the restore progress bar to show incorrect information. In addition, if a data file could not be loaded completely, then errors would also be reported for some…
fixBugfix #4626: Improve reliability of restoring large files In some cases restic failed to restore large files that frequently contain the same file chunk. In combination with certain backends, this could result in network connection timeouts that caused incomplete restores. Restic now includes…
fixFix: Restore ARMv5 support for ARM binaries
fixFix: Repair documentation build on Read the Docs
breakingBugfix #4540: Restore ARMv5 support for ARM binaries The official release binaries for restic 0.16.1 were accidentally built to require ARMv7. The build process is now updated to restore support for ARMv5. Please note that restic 0.17.0 will drop support for ARMv5 and require at least ARMv6.
fixBugfix #4545: Repair documentation build on Read the Docs For restic 0.16.1, no documentation was available at https://restic.readthedocs.io/ . The documentation build process is now updated to work again.
fixFix: Make key list command honor --no-lock
fixFix: Do not try to load password on command line autocomplete
fixFix: Update zstd library to fix possible data corruption at max. compression
otherChg: Update dependencies and require Go 1.19 or newer
otherEnh: Show progress bar while loading the index
otherEnh: Automatically set GOMAXPROCS in resource-constrained containers
featureEnh: Allow setting REST password and username via environment variables
otherEnh: Include inode numbers in JSON output for find and ls commands
featureEnh: Add config option to set SFTP command arguments
fixBugfix #4513: Make key list command honor --no-lock The key list command now supports the --no-lock options. This allows determining which keys a repo can be accessed by without the need for having write access (e.g., read-only sftp access, filesystem snapshot).
fixBugfix #4516: Do not try to load password on command line autocomplete The command line autocompletion previously tried to load the repository password. This could cause the autocompletion not to work. Now, this step gets skipped.
fixBugfix #4523: Update zstd library to fix possible data corruption at max. compression In restic 0.16.0, backups where the compression level was set to max (using --compression max) could in rare and very specific circumstances result in data corruption due to a bug in the library used for…
featureChange #4532: Update dependencies and require Go 1.19 or newer We have updated all dependencies. Since some libraries require newer Go standard library features, support for Go 1.18 has been dropped, which means that restic now requires at least Go 1.19 to build.
otherEnhancement #229: Show progress bar while loading the index Restic did not provide any feedback while loading index files. Now, there is a progress bar that shows the index loading progress.
otherEnhancement #4128: Automatically set GOMAXPROCS in resource-constrained containers When running restic in a Linux container with CPU-usage limits, restic now automatically adjusts GOMAXPROCS. This helps to reduce the memory consumption on hosts with many CPU cores.
featureEnhancement #4480: Allow setting REST password and username via environment variables Previously, it was only possible to specify the REST-server username and password in the repository URL, or by using the --repository-file option. This meant it was not possible to use authentication in contexts…
otherEnhancement #4511: Include inode numbers in JSON output for find and ls commands Restic used to omit the inode numbers in the JSON messages emitted for nodes by the ls command as well as for matches by the find command. It now includes those values whenever they are available.
featureEnhancement #4519: Add config option to set SFTP command arguments When using the sftp backend, scenarios where a custom identity file was needed for the SSH connection, required the full command to be specified: -o sftp.command='ssh user@host:port -i /ssh/my_private_key -s sftp' Now, the -o…
fixFix: Support "unlimited" in forget --keep-* options
fixFix: Support non-UTF8 paths as symlink target
fixFix: Avoid lock refresh issues on slow network connections
fixFix: Improve lock refresh handling after standby
fixFix: Correctly clean up status bar output of the backup command
fixFix: generate and init no longer silently ignore unexpected arguments
fixFix: Ignore missing folders in rest backend
fixChg: Fix JSON message type of scan_finished for the backup command
otherChg: Require Go 1.20 for Solaris builds
otherEnh: Show progress bar during restore
featureEnh: Add --retry-lock option
otherEnh: Sort snapshots by timestamp in restic find
featureEnh: Add repair index and repair snapshots commands
featureEnh: Allow certificate paths to be passed through environment variables
featureEnh: Add support for non-global Azure clouds
featureEnh: Add support for Managed / Workload Identity to azure backend
featureEnh: Add --human-readable option to ls and find commands
featureEnh: Add jq binary to Docker image
featureEnh: Allow specifying region of new buckets in the gs backend
featureEnh: Add support for extended attributes on symlinks
fixBugfix #2565: Support "unlimited" in forget --keep- options Restic would previously forget snapshots that should have been kept when a negative value was passed to the --keep- options. Negative values are now forbidden. To keep all snapshots, the special value unlimited is now supported. For…
fixBugfix #3311: Support non-UTF8 paths as symlink target Earlier restic versions did not correctly backup and restore symlinks that contain a non-UTF8 target. Note that this only affected systems that still use a non-Unicode encoding for filesystem paths. The repository format is now extended to add…
fixBugfix #4199: Avoid lock refresh issues on slow network connections On network connections with a low upload speed, backups and other operations could fail with the error message Fatal: failed to refresh lock in time. This has now been fixed by reworking the lock refresh handling.
fixBugfix #4274: Improve lock refresh handling after standby If the restic process was stopped or the host running restic entered standby during a long running operation such as a backup, this previously resulted in the operation failing with Fatal: failed to refresh lock in time. This has now been…
fixBugfix #4319: Correctly clean up status bar output of the backup command Due to a regression in restic 0.15.2, the status bar of the backup command could leave some output behind. This happened if filenames were printed that are wider than the current terminal width. This has now been fixed.
fixBugfix #4333: generate and init no longer silently ignore unexpected arguments
fixBugfix #4400: Ignore missing folders in rest backend If a repository accessed via the REST backend was missing folders, then restic would fail with an error while trying to list the data in the repository. This has been now fixed.
fixChange #4176: Fix JSON message type of scan_finished for the backup command Restic incorrectly set the message_type of the scan_finished message to status instead of verbose_status. This has now been corrected so that the messages report the correct type.
featureEnhancement #719: Add --retry-lock option This option allows specifying a duration for which restic will wait if the repository is already locked.
deprecatedEnhancement #1759: Add repair index and repair snapshots commands The rebuild-index command has been renamed to repair index. The old name will still work, but is deprecated. When a snapshot was damaged, the only option up to now was to completely forget the snapshot, even if only some unimportant…
featureEnhancement #1926: Allow certificate paths to be passed through environment variables Restic will now read paths to certificates from the environment variables RESTIC_CACERT or RESTIC_TLS_CLIENT_CERT if --cacert or --tls-client-cert are not specified.
featureEnhancement #2468: Add support for non-global Azure clouds The azure backend previously only supported storages using the global domain core.windows.net. This meant that backups to other domains such as Azure China (core.chinacloudapi.cn) or Azure Germany (core.cloudapi.de) were not supported.…
featureEnhancement #3698: Add support for Managed / Workload Identity to azure backend Restic now additionally supports authenticating to Azure using Workload Identity or Managed Identity credentials, which are automatically injected in several environments such as a managed Kubernetes cluster.
featureEnhancement #3871: Support : syntax to select subfolders Commands like diff or restore always worked with the full snapshot. This did not allow comparing only a specific subfolder or only restoring that folder (restore --include subfolder filters the restored files, but still creates the…
featureEnhancement #3941: Support --group-by for backup parent selection Previously, the backup command by default selected the parent snapshot based on the hostname and the backup targets. When the backup path list changed, the backup command was unable to determine a suitable parent snapshot and had to…
breakingEnhancement #4130: Cancel current command if cache becomes unusable If the cache directory was removed or ran out of space while restic was running, this would previously cause further caching attempts to fail and thereby drastically slow down the command execution. Now, the currently running…
featureEnhancement #4159: Add --human-readable option to ls and find commands Previously, when using the -l option with the ls and find commands, the displayed size was always in bytes, without an option for a more human readable format such as MiB or GiB. The new --human-readable option will convert…
featureEnhancement #4220: Add jq binary to Docker image The Docker image now contains jq, which can be useful to process JSON data output by restic.
featureEnhancement #4226: Allow specifying region of new buckets in the gs backend Previously, buckets used by the Google Cloud Storage backend would always get created in the "us" region. It is now possible to specify the region where a bucket should be created by using the -o gs.region=us option.
securityEnhancement #4375: Add support for extended attributes on symlinks Restic now supports extended attributes on symlinks when backing up, restoring, or FUSE-mounting snapshots. This includes, for example, the security.selinux xattr on Linux distributions that use SELinux.
+18 more items in the release notessecuritySec: Update golang.org/x/net to address CVE-2022-41723
fixFix: Sanitize filenames printed by backup during processing
fixFix: Make dump interpret --host and --path correctly
fixFix: Correct number of blocks reported in mount point
fixFix: Minimize risk of spurious filesystem loops with mount
featureEnh: Add release binaries for riscv64 architecture on Linux
otherEnh: Upgrade Minio to version 7.0.49
securitySecurity #4275: Update golang.org/x/net to address CVE-2022-41723
fixBugfix #2260: Sanitize filenames printed by backup during processing The backup command would previously not sanitize the filenames it printed during processing, potentially causing newlines or terminal control characters to mangle the status output or even change the state of a terminal.…
fixBugfix #4211: Make dump interpret --host and --path correctly A regression in restic 0.15.0 caused dump to confuse its --host= and --path= options: it looked for snapshots with paths called from hosts called . It now treats the options as intended.
fixBugfix #4239: Correct number of blocks reported in mount point Restic mount points reported an incorrect number of 512-byte (POSIX standard) blocks for files and links due to a rounding bug. In particular, empty files were reported as taking one block instead of zero. The rounding is now fixed:…
fixBugfix #4253: Minimize risk of spurious filesystem loops with mount When a backup contains a directory that has the same name as its parent, say a/b/b, and the GNU find command was run on this backup in a restic mount, find would refuse to traverse the lowest b directory, instead printing File…
featureEnhancement #4180: Add release binaries for riscv64 architecture on Linux Builds for the riscv64 architecture on Linux are now included in the release binaries.
featureEnhancement #4219: Upgrade Minio to version 7.0.49 The upgraded version now allows use of the ap-southeast-4 region (Melbourne).
fixFix: Remove b2_download_file_by_name: 404 warning from B2 backend
fixFix: Make prune --quiet not print progress bar
fixFix: Make self-update --output work with new filename on Windows
fixFix: Add missing ETA in backup progress bar
otherEnh: Ignore empty lock files
breakingBugfix #3750: Remove b2_download_file_by_name: 404 warning from B2 backend In some cases the B2 backend could print b2_download_file_by_name: 404: : b2.b2err warnings. These are only debug messages and can be safely ignored. Restic now uses an updated library for accessing B2, which removes the…
fixBugfix #4147: Make prune --quiet not print progress bar A regression in restic 0.15.0 caused prune --quiet to show a progress bar while deciding how to process each pack files. This has now been fixed.
fixBugfix #4163: Make self-update --output work with new filename on Windows Since restic 0.14.0 the self-update command did not work when a custom output filename was specified via the --output option. This has now been fixed. As a workaround, either use an older restic version to run the…
fixBugfix #4167: Add missing ETA in backup progress bar A regression in restic 0.15.0 caused the ETA to be missing from the progress bar displayed by the backup command. This has now been fixed.
featureEnhancement #4143: Ignore empty lock files With restic 0.15.0 the checks for stale locks became much stricter than before. In particular, empty or unreadable locks were no longer silently ignored. This made restic to complain with Load(, 0, 0) returned error, retrying after 552.330144ms: load():…