Repository navigation
chore(deps): update all dependencies - #904
Merged
Merged
Conversation
doa-renovate
Bot
force-pushed
the
renovate/all
branch
from
November 19, 2026 13:35
923230e to
4f7de58
Compare
doa-renovate
Bot
force-pushed
the
renovate/all
branch
from
November 19, 2026 13:50
4f7de58 to
0af3648
Compare
doa-renovate
Bot
force-pushed
the
renovate/all
branch
from
November 19, 2026 14:05
0af3648 to
8bb3ab2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
26.10.6.18→26.10.7.2444.253.0→44.253.2v0.19.1→v0.20.0Release Notes
renovatebot/renovate (ghcr.io/renovatebot/renovate)
v44.253.2Compare Source
Bug Fixes
v44.253.1Compare Source
Bug Fixes
Code Refactoring
restic/restic
v0.20.0: restic 0.20.0Compare Source
Changelog for restic 0.20.0 (2026-11-19)
The following sections list the changes in restic 0.20.0 relevant to restic users. The changes are ordered by importance.
Summary
restore --ownership-by-namecannot resolve namesrestoreswiftbackend password in debug log outputstatsprogress bar counters for every snapshotprunefails to list pack files--keep-within*durationsprunecommandcheckon the S3 backendlist packscommandb2backendrepair packsbackupin verbose modefind --packrepair snapshots --forgetremove broken snapshotsDetails
Security #22178: Fix ownership when
restore --ownership-by-namecannot resolve namesWhen restoring with
--ownership-by-name, user or group names that could not be resolved on the restore host (or were not recorded in the snapshot) caused restic to change the owner of the restored file to UID/GID 0. Combined with restored setuid/setgid bits this could produce unintentional setuid-root files.Restic now instead falls back to the numeric UID/GID stored in the snapshot and prints a warning when a name cannot be resolved.
#22178 #22185
Security #22180: Reject duplicate or out-of-order node names during
restoreA tree containing a symlink and a directory with the same name could let
restorewrite through the symlink to files outside the restore target.Restic now rejects trees whose node names are not strictly increasing during restore and reports an error instead of restoring such a snapshot.
Thanks to Mario Ramos (@marrionesa), Zachariah Mithani (AploSec), Manuel Riel (@m3nu) and calif.io for reporting this.
#22180 #22190
Bugfix #21977: Don't crash on truncated key or config file
Restic previously crashed with a slice bounds panic when the repository contained a key or config file that was shorter than the encryption overhead, for example after an upload was interrupted. Since every command has to read a key file, the whole repository became unusable until the file was removed.
This has now been fixed, and restic instead reports that the file is too short.
#21977
Bugfix #22007: Redact
swiftbackend password in debug log outputRestic could previously write the OpenStack Swift backend password in clear text to the debug log when debug logging was enabled. The password came from the environment variables
OS_PASSWORDandST_KEY. It is now redacted.#22007
Bugfix #22051: Reject empty repository location files
Previously, if the
--repository-fileoption orRESTIC_REPOSITORY_FILEenvironment variable referred to a file that was either empty or contained only whitespace, restic used the current directory for the repository.This has now been fixed, and restic instead reports an error in this case.
#22051 #22052
Bugfix #22085: Restore partially matching hard-linked files correctly
When restoring over an existing file which had hard links and was partially different from the file in the snapshot, restic used to replace the file with an empty one but only restored the changed parts. The restored file then contained zero bytes in the unchanged parts. Restic now instead rewrites the whole file in this case.
#22085 #22086
Bugfix #22092: Handle empty directories from older repaired snapshots
Since restic 0.19.0, snapshots containing empty directories written by older versions of
repair snapshotscould fail witherror decoding tree: expected [, got <nil>.This has now been fixed, allowing
prune,checkandrestoreto process the affected snapshots successfully.#22092 #22117
Bugfix #22112: Don't reset
statsprogress bar counters for every snapshotThe progress bar of the
statscommand previously reset its file, blob and size counters at the start of each snapshot, so the final progress line only showed the numbers for the last processed snapshot. These numbers varied between runs depending on the order in which snapshots were processed.The progress bar now instead counts across all selected snapshots.
#22112 #22130
Bugfix #22120: Improve error message when
prunefails to list pack filesWhen listing the pack files of a repository failed during
prune, for example due to a request timeout, restic printed the error together with a stack trace.Restic now instead reports a short error message stating that listing the pack files failed.
#22120 #22124
Bugfix #22136: Improve resilience of repository v2 upgrade rollback
When an upgrade from repository version 1 to version 2 failed, restic deleted the configuration file before writing the previous version of it back. If writing the old configuration file back also failed, the repository no longer had a configuration file and could not be opened.
Restic now writes the previous configuration back without deleting the file first on relevant backends.
#22136
Bugfix #22163: Error on too large numbers in
--keep-within*durationsRestic used to crash with a stack trace when a number in a duration such as the one passed to
forget --keep-withindid not fit into an integer. It now reports an invalid argument instead.#22163
Bugfix #22181: Do not delete files in directories whose tree cannot be loaded
When
restore --deletefailed to load or read the tree of a directory, for example because a pack file was missing, restic reported an error but then deleted all existing content of that directory in the target. Restic now disables deletion for the rest of the restore when a tree cannot be loaded.#22181 #22189
Change #22104: Require Go 1.26.10 or newer
Restic now requires Go 1.26.10 or newer to build, as the library used to access the B2 backend requires it.
#22104 #22121
Enhancement #3129: Add JSON support to
prunecommandThe
prunecommand now supports the--jsonoption for JSON output.#3129 #5239
Enhancement #5189: Add option to disable AWS S3 dual-stack endpoints
Restic used dual-stack endpoints for AWS regions that have them, with no way to opt out. VPC interface and gateway endpoints do not support dual-stack, so a repository reachable over a VPC endpoint could not be used.
Passing
-o s3.disable-dualstack=truenow keeps restic on the single-stack endpoint.#5189 #22060
Enhancement #5248: Add warmup support for
checkon the S3 backendThe
checkcommand can now warm up pack files from cold storage on S3 and S3-compatible providers before reading them. Like the other cold storage features, this remains experimental and is gated behind thes3-restorefeature flag.#3202 #2504 #5248
Enhancement #5372: Support specifying snapshot ID in
list packscommandThe
list packscommand now accepts a snapshot ID and lists the pack files used by that snapshot.#5372 #5396
Enhancement #5741: Support Multi-Bucket Application Keys in the
b2backendThe
b2backend now supports Backblaze B2 Multi-Bucket Application Keys, including single-bucket keys created through the multi-bucket API (for example by the Backblaze Terraform provider).#5741 #22104
Enhancement #21845: Handle missing pack files in
repair packsMissing and damaged pack files previously required separate approaches to fix a repository. Both cases can now be handled by the
repair packscommand, which removes missing pack files from the repository index.#21845
Enhancement #21870: Show excluded items during
backupin verbose modeThe
backup -vvcommand (backup in verbose mode) now shows excluded files and directories. Both text and JSON output are supported.#21870 #21887
Enhancement #21883: Handle corrupted pack files in
find --packThe
find --pack <id>command can now also report snapshots in which a pack file is corrupted but still present in the repository index.#21883
Enhancement #21892: Make
repair snapshots --forgetremove broken snapshotsThe
repair snapshots --forgetcommand will now remove broken snapshot files reported bycheckor by earlier error messages from restic.#21892 #21907
Enhancement #21937: Reduce memory usage of the in-memory index
Restic keeps an index of the repository contents in memory during most operations. This index now requires roughly 12% less memory, which is especially noticeable for large repositories with many snapshots, where a lot of index data has to be loaded.
#21937
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate CLI.