Skip to content

restic 0.7.1
Compare
Choose a tag to compare
@fd0 fd0 released this 22 Jul 09:17
· 6380 commits to master since this release
v0.7.1
This tag was signed with the committer’s verified signature.
fd0 Alexander Neumann
GPG key ID: 91A6868BD3F7A907
Verified
Learn about vigilant mode.
04cfb98

UPDATE

After releasing restic 0.7.1, we've discovered a serious bug that was more or less accidentally corrected in 0.7.1, the background story is described in our blog. Do not use restic 0.7.0, upgrade to at least 0.7.1

And now the original release notes text:

We're proud to present restic 0.7.1. The binaries released with each restic version starting are reproducible, which means that you can easily reproduce a byte identical version from the source code for that release. Instructions on how to do that are contained in the builder repository.

Important Changes in 0.7.1

  • The migrate command for chaning the s3legacy layout to the default layout for s3 backends has been improved: It can now be restarted with restic migrate --force s3_layout and automatically retries operations on error. #1073 #1075

Small changes

  • The local and sftp backends now create the subdirs below data/ on open/init. This way, restic makes sure that they always exist. This is connected to an issue for the sftp server: restic/rest-server#11 (comment) #1055 #1077 #1105

  • When no S3 credentials are specified in the environment variables, restic now tries to load credentials from an IAM instance profile when the s3 backend is used. #1067 #1086

  • On Darwin and FreeBSD, restic now prints stats when SIGINFO is received (usually when ctrl+t is pressed). #1082

  • The dependencies have been updated. #1108 #1124

  • A bug was found (and corrected) in the index rebuilding after prune, which led to indexes which include blobs that were not present in the repo any more. There were already checks in place which detected this situation and aborted with an error message. A new run of either prune or rebuild-index corrected the index files. This is now fixed and a test has been added to detect this. #1115

  • Errors for chmod() on Unix for filesystems which do not support it (e.g. smb mounted via gvfs) are now ignored. #1080 #1112

  • The semantic for the --tags option to forget and snapshots was clarified: #1081 #1090

Assets 19
Loading