[ ] PR contains the label that identifies the area, one of: area:operator, area:chart
[ ] If the PR is targeting a Helm chart, add the chart label, e.g. chart:k8up
Release Notes
restic/restic (github.com/restic/restic)
### [`v0.16.4`](https://togithub.com/restic/restic/releases/tag/v0.16.4): restic 0.16.4
[Compare Source](https://togithub.com/restic/restic/compare/v0.16.3...v0.16.4)
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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst).
# Changelog for restic 0.16.4 (2024-02-04)
The following sections list the changes in restic 0.16.4 relevant to restic users. The changes are ordered by importance.
## Summary
- Fix [#4677](https://togithub.com/restic/restic/issues/4677): Downgrade zstd library to fix rare data corruption at max. compression
- Enh [#4529](https://togithub.com/restic/restic/issues/4529): Add extra verification of data integrity before upload
## Details
- Bugfix [#4677](https://togithub.com/restic/restic/issues/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 compressing data. Restic 0.16.1 and 0.16.2 were not affected.
Restic now uses the previous version of the library used to compress data, the same version used by restic 0.16.2. Please note that the `auto` compression level (which restic uses by default) was never affected, and even if you used `max` compression, chances of being affected by this issue are small.
To check a repository for any corruption, run `restic check --read-data`. This will download and verify the whole repository and can be used at any time to completely verify the integrity of a repository. If the `check` command detects anomalies, follow the suggested steps.
[#4677](https://togithub.com/restic/restic/issues/4677) [#4679](https://togithub.com/restic/restic/pull/4679)
- Enhancement [#4529](https://togithub.com/restic/restic/issues/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 --read-data` or `check --read-data-subset` commands.
To further ensure data integrity, even in the case of hardware issues or software bugs, restic now performs additional verification of the files about to be uploaded to the repository.
These extra checks will increase CPU usage during backups. They can therefore, if absolutely necessary, be disabled using the `--no-extra-verify` global option. Please note that this should be combined with more active checking using the previously mentioned check commands.
[#4529](https://togithub.com/restic/restic/issues/4529) [#4681](https://togithub.com/restic/restic/pull/4681)
### [`v0.16.3`](https://togithub.com/restic/restic/releases/tag/v0.16.3): restic 0.16.3
[Compare Source](https://togithub.com/restic/restic/compare/v0.16.2...v0.16.3)
This release fixes a couple of bugs on Windows and in the `restore` command. It also works around an unlikely yet possible situation with `rclone` which could potentially result in data loss.
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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst).
# Changelog for restic 0.16.3 (2024-01-14)
The following sections list the changes in restic 0.16.3 relevant to restic users. The changes are ordered by importance.
## Summary
- Fix [#4560](https://togithub.com/restic/restic/issues/4560): Improve errors for irregular files on Windows
- Fix [#4574](https://togithub.com/restic/restic/issues/4574): Support backup of deduplicated files on Windows again
- Fix [#4612](https://togithub.com/restic/restic/issues/4612): Improve error handling for `rclone` backend
- Fix [#4624](https://togithub.com/restic/restic/pull/4624): Correct `restore` progress information if an error occurs
- Fix [#4626](https://togithub.com/restic/restic/pull/4626): Improve reliability of restoring large files
## Details
- Bugfix [#4560](https://togithub.com/restic/restic/issues/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 the relevant file path: `error: nodeFromFileInfo path/to/file: unsupported file type "irregular"`. As irregular files are not required to behave like regular files, it is not possible to provide a generic way to back up those files.
[#4560](https://togithub.com/restic/restic/issues/4560) [#4620](https://togithub.com/restic/restic/pull/4620) https://forum.restic.net/t/windows-backup-error-invalid-node-type/6875
- Bugfix [#4574](https://togithub.com/restic/restic/issues/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 1.21.0-1.21.4.
The Go version used to build restic has now been updated to fix this.
[#4574](https://togithub.com/restic/restic/issues/4574) [#4621](https://togithub.com/restic/restic/pull/4621)
- Bugfix [#4612](https://togithub.com/restic/restic/issues/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 when the `prune` command is listing existing snapshots.
Error handling has now been improved to detect and work around this case.
[#4612](https://togithub.com/restic/restic/issues/4612) [#4618](https://togithub.com/restic/restic/pull/4618)
- Bugfix [#4624](https://togithub.com/restic/restic/issues/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 already restored files.
Error reporting of the `restore` command has now been made more accurate.
[#4624](https://togithub.com/restic/restic/pull/4624) https://forum.restic.net/t/errors-restoring-with-restic-on-windows-server-s3/6943
- Bugfix [#4626](https://togithub.com/restic/restic/issues/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 special handling for such file chunks to ensure reliable restores.
[#4626](https://togithub.com/restic/restic/pull/4626) https://forum.restic.net/t/errors-restoring-with-restic-on-windows-server-s3/6943
### [`v0.16.2`](https://togithub.com/restic/restic/releases/tag/v0.16.2): restic 0.16.2
[Compare Source](https://togithub.com/restic/restic/compare/v0.16.1...v0.16.2)
restic 0.16.2 restores support for ARMv5 which was accidentally not included in the previous one, and also fixes missing documentation on [Read the Docs](https://restic.readthedocs.io/).
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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst).
# Changelog for restic 0.16.2 (2023-10-29)
The following sections list the changes in restic 0.16.2 relevant to restic users. The changes are ordered by importance.
## Summary
- Fix [#4540](https://togithub.com/restic/restic/issues/4540): Restore ARMv5 support for ARM binaries
- Fix [#4545](https://togithub.com/restic/restic/pull/4545): Repair documentation build on Read the Docs
## Details
- Bugfix [#4540](https://togithub.com/restic/restic/issues/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.
[#4540](https://togithub.com/restic/restic/issues/4540)
- Bugfix [#4545](https://togithub.com/restic/restic/issues/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.
[#4545](https://togithub.com/restic/restic/pull/4545)
### [`v0.16.1`](https://togithub.com/restic/restic/releases/tag/v0.16.1): restic 0.16.1
[Compare Source](https://togithub.com/restic/restic/compare/v0.16.0...v0.16.1)
restic 0.16.1 has been released! It contains a few usage and cosmetic improvements, but also one bugfix for a very unlikely but still possible data corruption issue when using the max compression level. Please read the changelog for more details and information on how to verify your repository if you used max compression. Please also note that the auto compression level (which is the default) was never 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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst).
# Changelog for restic 0.16.1 (2023-10-24)
The following sections list the changes in restic 0.16.1 relevant to restic users. The changes are ordered by importance.
## Summary
- Fix [#4513](https://togithub.com/restic/restic/issues/4513): Make `key list` command honor `--no-lock`
- Fix [#4516](https://togithub.com/restic/restic/issues/4516): Do not try to load password on command line autocomplete
- Fix [#4523](https://togithub.com/restic/restic/issues/4523): Update zstd library to fix possible data corruption at max. compression
- Chg [#4532](https://togithub.com/restic/restic/pull/4532): Update dependencies and require Go 1.19 or newer
- Enh [#229](https://togithub.com/restic/restic/issues/229): Show progress bar while loading the index
- Enh [#4128](https://togithub.com/restic/restic/issues/4128): Automatically set `GOMAXPROCS` in resource-constrained containers
- Enh [#4480](https://togithub.com/restic/restic/pull/4480): Allow setting REST password and username via environment variables
- Enh [#4511](https://togithub.com/restic/restic/pull/4511): Include inode numbers in JSON output for `find` and `ls` commands
- Enh [#4519](https://togithub.com/restic/restic/pull/4519): Add config option to set SFTP command arguments
## Details
- Bugfix [#4513](https://togithub.com/restic/restic/issues/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).
[#4513](https://togithub.com/restic/restic/issues/4513) [#4514](https://togithub.com/restic/restic/pull/4514)
- Bugfix [#4516](https://togithub.com/restic/restic/issues/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.
[#4516](https://togithub.com/restic/restic/issues/4516) [#4526](https://togithub.com/restic/restic/pull/4526)
- Bugfix [#4523](https://togithub.com/restic/restic/issues/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 compressing data.
Restic now uses the latest version of the library used to compress data, which includes a fix for this issue. Please note that the `auto` compression level (which restic uses by default) was never affected, and even if you used `max` compression, chances of being affected by this issue were very small.
To check a repository for any corruption, run `restic check --read-data`. This will download and verify the whole repository and can be used at any time to completely verify the integrity of a repository. If the `check` command detects anomalies, follow the suggested steps.
To simplify any needed repository repair and minimize data loss, there is also a new and experimental `repair packs` command that salvages all valid data from the affected pack files (see `restic help repair packs` for more information).
[#4523](https://togithub.com/restic/restic/issues/4523) [#4530](https://togithub.com/restic/restic/pull/4530)
- Change [#4532](https://togithub.com/restic/restic/issues/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.
[#4532](https://togithub.com/restic/restic/pull/4532) [#4533](https://togithub.com/restic/restic/pull/4533)
- Enhancement [#229](https://togithub.com/restic/restic/issues/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.
[#229](https://togithub.com/restic/restic/issues/229) [#4419](https://togithub.com/restic/restic/pull/4419)
- Enhancement [#4128](https://togithub.com/restic/restic/issues/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.
[#4128](https://togithub.com/restic/restic/issues/4128) [#4485](https://togithub.com/restic/restic/pull/4485) [#4531](https://togithub.com/restic/restic/pull/4531)
- Enhancement [#4480](https://togithub.com/restic/restic/issues/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 where the repository URL is stored in publicly accessible way.
Restic now allows setting the username and password using the `RESTIC_REST_USERNAME` and `RESTIC_REST_PASSWORD` variables.
[#4480](https://togithub.com/restic/restic/pull/4480)
- Enhancement [#4511](https://togithub.com/restic/restic/issues/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.
[#4511](https://togithub.com/restic/restic/pull/4511)
- Enhancement [#4519](https://togithub.com/restic/restic/issues/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 sftp.args=...` option can be passed to restic to specify custom arguments for the SSH command executed by the SFTP backend. This simplifies the above example to `-o sftp.args='-i /ssh/my_private_key'`.
[#4241](https://togithub.com/restic/restic/issues/4241) [#4519](https://togithub.com/restic/restic/pull/4519)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v0.16.0->v0.16.4area:operator,area:chartchart:k8upRelease Notes
restic/restic (github.com/restic/restic)
### [`v0.16.4`](https://togithub.com/restic/restic/releases/tag/v0.16.4): restic 0.16.4 [Compare Source](https://togithub.com/restic/restic/compare/v0.16.3...v0.16.4) 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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst). # Changelog for restic 0.16.4 (2024-02-04) The following sections list the changes in restic 0.16.4 relevant to restic users. The changes are ordered by importance. ## Summary - Fix [#4677](https://togithub.com/restic/restic/issues/4677): Downgrade zstd library to fix rare data corruption at max. compression - Enh [#4529](https://togithub.com/restic/restic/issues/4529): Add extra verification of data integrity before upload ## Details - Bugfix [#4677](https://togithub.com/restic/restic/issues/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 compressing data. Restic 0.16.1 and 0.16.2 were not affected. Restic now uses the previous version of the library used to compress data, the same version used by restic 0.16.2. Please note that the `auto` compression level (which restic uses by default) was never affected, and even if you used `max` compression, chances of being affected by this issue are small. To check a repository for any corruption, run `restic check --read-data`. This will download and verify the whole repository and can be used at any time to completely verify the integrity of a repository. If the `check` command detects anomalies, follow the suggested steps. [#4677](https://togithub.com/restic/restic/issues/4677) [#4679](https://togithub.com/restic/restic/pull/4679) - Enhancement [#4529](https://togithub.com/restic/restic/issues/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 --read-data` or `check --read-data-subset` commands. To further ensure data integrity, even in the case of hardware issues or software bugs, restic now performs additional verification of the files about to be uploaded to the repository. These extra checks will increase CPU usage during backups. They can therefore, if absolutely necessary, be disabled using the `--no-extra-verify` global option. Please note that this should be combined with more active checking using the previously mentioned check commands. [#4529](https://togithub.com/restic/restic/issues/4529) [#4681](https://togithub.com/restic/restic/pull/4681) ### [`v0.16.3`](https://togithub.com/restic/restic/releases/tag/v0.16.3): restic 0.16.3 [Compare Source](https://togithub.com/restic/restic/compare/v0.16.2...v0.16.3) This release fixes a couple of bugs on Windows and in the `restore` command. It also works around an unlikely yet possible situation with `rclone` which could potentially result in data loss. 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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst). # Changelog for restic 0.16.3 (2024-01-14) The following sections list the changes in restic 0.16.3 relevant to restic users. The changes are ordered by importance. ## Summary - Fix [#4560](https://togithub.com/restic/restic/issues/4560): Improve errors for irregular files on Windows - Fix [#4574](https://togithub.com/restic/restic/issues/4574): Support backup of deduplicated files on Windows again - Fix [#4612](https://togithub.com/restic/restic/issues/4612): Improve error handling for `rclone` backend - Fix [#4624](https://togithub.com/restic/restic/pull/4624): Correct `restore` progress information if an error occurs - Fix [#4626](https://togithub.com/restic/restic/pull/4626): Improve reliability of restoring large files ## Details - Bugfix [#4560](https://togithub.com/restic/restic/issues/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 the relevant file path: `error: nodeFromFileInfo path/to/file: unsupported file type "irregular"`. As irregular files are not required to behave like regular files, it is not possible to provide a generic way to back up those files. [#4560](https://togithub.com/restic/restic/issues/4560) [#4620](https://togithub.com/restic/restic/pull/4620) https://forum.restic.net/t/windows-backup-error-invalid-node-type/6875 - Bugfix [#4574](https://togithub.com/restic/restic/issues/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 1.21.0-1.21.4. The Go version used to build restic has now been updated to fix this. [#4574](https://togithub.com/restic/restic/issues/4574) [#4621](https://togithub.com/restic/restic/pull/4621) - Bugfix [#4612](https://togithub.com/restic/restic/issues/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 when the `prune` command is listing existing snapshots. Error handling has now been improved to detect and work around this case. [#4612](https://togithub.com/restic/restic/issues/4612) [#4618](https://togithub.com/restic/restic/pull/4618) - Bugfix [#4624](https://togithub.com/restic/restic/issues/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 already restored files. Error reporting of the `restore` command has now been made more accurate. [#4624](https://togithub.com/restic/restic/pull/4624) https://forum.restic.net/t/errors-restoring-with-restic-on-windows-server-s3/6943 - Bugfix [#4626](https://togithub.com/restic/restic/issues/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 special handling for such file chunks to ensure reliable restores. [#4626](https://togithub.com/restic/restic/pull/4626) https://forum.restic.net/t/errors-restoring-with-restic-on-windows-server-s3/6943 ### [`v0.16.2`](https://togithub.com/restic/restic/releases/tag/v0.16.2): restic 0.16.2 [Compare Source](https://togithub.com/restic/restic/compare/v0.16.1...v0.16.2) restic 0.16.2 restores support for ARMv5 which was accidentally not included in the previous one, and also fixes missing documentation on [Read the Docs](https://restic.readthedocs.io/). 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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst). # Changelog for restic 0.16.2 (2023-10-29) The following sections list the changes in restic 0.16.2 relevant to restic users. The changes are ordered by importance. ## Summary - Fix [#4540](https://togithub.com/restic/restic/issues/4540): Restore ARMv5 support for ARM binaries - Fix [#4545](https://togithub.com/restic/restic/pull/4545): Repair documentation build on Read the Docs ## Details - Bugfix [#4540](https://togithub.com/restic/restic/issues/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. [#4540](https://togithub.com/restic/restic/issues/4540) - Bugfix [#4545](https://togithub.com/restic/restic/issues/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. [#4545](https://togithub.com/restic/restic/pull/4545) ### [`v0.16.1`](https://togithub.com/restic/restic/releases/tag/v0.16.1): restic 0.16.1 [Compare Source](https://togithub.com/restic/restic/compare/v0.16.0...v0.16.1) restic 0.16.1 has been released! It contains a few usage and cosmetic improvements, but also one bugfix for a very unlikely but still possible data corruption issue when using the max compression level. Please read the changelog for more details and information on how to verify your repository if you used max compression. Please also note that the auto compression level (which is the default) was never 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://togithub.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://togithub.com/restic/restic/blob/master/doc/developer_information.rst). # Changelog for restic 0.16.1 (2023-10-24) The following sections list the changes in restic 0.16.1 relevant to restic users. The changes are ordered by importance. ## Summary - Fix [#4513](https://togithub.com/restic/restic/issues/4513): Make `key list` command honor `--no-lock` - Fix [#4516](https://togithub.com/restic/restic/issues/4516): Do not try to load password on command line autocomplete - Fix [#4523](https://togithub.com/restic/restic/issues/4523): Update zstd library to fix possible data corruption at max. compression - Chg [#4532](https://togithub.com/restic/restic/pull/4532): Update dependencies and require Go 1.19 or newer - Enh [#229](https://togithub.com/restic/restic/issues/229): Show progress bar while loading the index - Enh [#4128](https://togithub.com/restic/restic/issues/4128): Automatically set `GOMAXPROCS` in resource-constrained containers - Enh [#4480](https://togithub.com/restic/restic/pull/4480): Allow setting REST password and username via environment variables - Enh [#4511](https://togithub.com/restic/restic/pull/4511): Include inode numbers in JSON output for `find` and `ls` commands - Enh [#4519](https://togithub.com/restic/restic/pull/4519): Add config option to set SFTP command arguments ## Details - Bugfix [#4513](https://togithub.com/restic/restic/issues/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). [#4513](https://togithub.com/restic/restic/issues/4513) [#4514](https://togithub.com/restic/restic/pull/4514) - Bugfix [#4516](https://togithub.com/restic/restic/issues/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. [#4516](https://togithub.com/restic/restic/issues/4516) [#4526](https://togithub.com/restic/restic/pull/4526) - Bugfix [#4523](https://togithub.com/restic/restic/issues/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 compressing data. Restic now uses the latest version of the library used to compress data, which includes a fix for this issue. Please note that the `auto` compression level (which restic uses by default) was never affected, and even if you used `max` compression, chances of being affected by this issue were very small. To check a repository for any corruption, run `restic check --read-data`. This will download and verify the whole repository and can be used at any time to completely verify the integrity of a repository. If the `check` command detects anomalies, follow the suggested steps. To simplify any needed repository repair and minimize data loss, there is also a new and experimental `repair packs` command that salvages all valid data from the affected pack files (see `restic help repair packs` for more information). [#4523](https://togithub.com/restic/restic/issues/4523) [#4530](https://togithub.com/restic/restic/pull/4530) - Change [#4532](https://togithub.com/restic/restic/issues/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. [#4532](https://togithub.com/restic/restic/pull/4532) [#4533](https://togithub.com/restic/restic/pull/4533) - Enhancement [#229](https://togithub.com/restic/restic/issues/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. [#229](https://togithub.com/restic/restic/issues/229) [#4419](https://togithub.com/restic/restic/pull/4419) - Enhancement [#4128](https://togithub.com/restic/restic/issues/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. [#4128](https://togithub.com/restic/restic/issues/4128) [#4485](https://togithub.com/restic/restic/pull/4485) [#4531](https://togithub.com/restic/restic/pull/4531) - Enhancement [#4480](https://togithub.com/restic/restic/issues/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 where the repository URL is stored in publicly accessible way. Restic now allows setting the username and password using the `RESTIC_REST_USERNAME` and `RESTIC_REST_PASSWORD` variables. [#4480](https://togithub.com/restic/restic/pull/4480) - Enhancement [#4511](https://togithub.com/restic/restic/issues/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. [#4511](https://togithub.com/restic/restic/pull/4511) - Enhancement [#4519](https://togithub.com/restic/restic/issues/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 sftp.args=...` option can be passed to restic to specify custom arguments for the SSH command executed by the SFTP backend. This simplifies the above example to `-o sftp.args='-i /ssh/my_private_key'`. [#4241](https://togithub.com/restic/restic/issues/4241) [#4519](https://togithub.com/restic/restic/pull/4519)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.