Merge branch 'patch-release'

2026-10-13 05:27:13 +00:00 · 2026-07-05 16:27:43 +02:00
commit d8ef26afa4
@@ -1,8 +0,0 @@
-Bugfix: Hide progress bar for stats command in JSON mode
-
-Since restic 0.19.0, the stats command shows a progress bar. However,
-it was also active when given the `--json` option resulting in text
-mixed with JSON. This has been fixed.
-
-https://github.com/restic/restic/issues/21866
-https://github.com/restic/restic/pull/21871
@@ -1,11 +0,0 @@
-Bugfix: Restore old behavior of `snapshots --latest <n>` without `--group-by`
-
-Restic 0.19.0 changed the behavior of `snapshots --latest <n>` to no longer
-group snapshots by default.
-
-`snapshots --latest <n>` has been reverted to the old behavior if `--group-by`
-is not specified. When specifying `--group-by`, the output is still grouped as
-requested like in restic 0.19.0.
-
-https://github.com/restic/restic/issues/21869
-https://github.com/restic/restic/pull/21875
@@ -1,9 +0,0 @@
-Bugfix: Remove read-only files via the SFTP backend on Windows servers
-
-Since restic 0.19.0, repository files on the SFTP backend are marked
-read-only after save. On Windows SFTP servers, removing them failed
-with a permission error. The SFTP backend now clears the read-only flag
-before removing the file.
-
-https://github.com/restic/restic/issues/21895
-https://github.com/restic/restic/pull/21897
@@ -1,9 +0,0 @@
-Bugfix: Fix excludes of duplicate directory entries during `backup`
-
-Since restic 0.19.0, creating a backup of a directory containing
-duplicate directory entries always resulted in "Warning: at least
-one source file could not be read" even if the files in question
-were excluded. This has been fixed.
-
-https://github.com/restic/restic/issues/21899
-https://github.com/restic/restic/pull/21900
@@ -1,12 +0,0 @@
-Bugfix: Prevent mounting over the repository directory
-
-Using a local repository directory as the `mount` target — or a path
-that contains it, or that it contains — caused the FUSE server to
-read its own backend files through the new mount, deadlocking the
-kernel and requiring a long reboot to recover.
-
-Restic now resolves both paths and refuses any such overlap with a
-clear error before mounting.
-
-https://github.com/restic/restic/issues/5234
-https://github.com/restic/restic/pull/5348
@@ -1,9 +0,0 @@
-Bugfix: Skip inaccessible `backup` source paths
-
-The `backup` command only skipped source paths that did not exist. A path that
-could not be accessed for another reason, such as a malformed path on Windows,
-was kept and produced an empty snapshot. Restic now skips any such path and
-aborts if none remain.
-
-https://github.com/restic/restic/issues/5667
-https://github.com/restic/restic/pull/21852
@@ -1,10 +0,0 @@
-Bugfix: Update `mount` latest symlink after snapshot reload
-
-When `restic mount` was kept running while new snapshots were
-created, the new snapshots appeared in the mountpoint, but the `latest`
-symlink could still point to the previously latest snapshot. Restic now
-invalidates the cached snapshot directory entries after a snapshot reload so
-that `latest` points to the newest snapshot.
-
-https://github.com/restic/restic/issues/5722
-https://github.com/restic/restic/pull/21873
@@ -1,8 +0,0 @@
-Bugfix: Show timezone location in `snapshots` output
-
-Since restic 0.19.0, the `snapshots` command printed the current timezone when
-listing snapshots. However, the timezone can change during the year, for example,
-due to daylight saving time. Instead just print the name of the current location.
-
-https://github.com/restic/restic/pull/21876
-https://forum.restic.net/t/possible-bug-in-timezone-naming/10867
@@ -1,7 +0,0 @@
-Bugfix: prevent crash in mountpoint validation if mountpoint is inaccessible
-
-Since restic 0.19.0, the `mount` command validates a mountpoint before loading
-the repository. If restic was unable to stat the mountpoint, this would result
-in a crash. This has been fixed to correctly return an error instead.
-
-https://github.com/restic/restic/pull/21879