chore(release): 3.4.1

This commit is contained in:
nvrl committed 2026-10-16 01:32:59 +02:00
1 parent a9cb389f04
commit 18cc2ea498
5 files changed
+18 -7

No files matched your search

Generated
+4 -4
View File
@@ -3474,7 +3474,7 @@ checksum = "2ee67f1008b1ba2321834326597b8e186293b049a023cdef258527550b9935b4"
[[package]]
name = "pdfs-cli"
version = "3.4.0"
version = "3.4.1"
dependencies = [
"anyhow",
"clap",
@@ -3490,7 +3490,7 @@ dependencies = [
[[package]]
name = "pdfs-core"
version = "3.4.0"
version = "3.4.1"
dependencies = [
"async-trait",
"base64 0.23.1",
@@ -3516,7 +3516,7 @@ dependencies = [
[[package]]
name = "pdfs-fuse"
version = "3.4.0"
version = "3.4.1"
dependencies = [
"async-trait",
"base64 0.23.1",
@@ -3538,7 +3538,7 @@ dependencies = [
[[package]]
name = "pdfs-gui"
version = "3.4.0"
version = "3.4.1"
dependencies = [
"anyhow",
"async-channel",
+1 -1
View File
@@ -3,7 +3,7 @@ resolver = "2"
members = ["crates/pdfs-core", "crates/pdfs-fuse", "crates/pdfs-cli", "crates/pdfs-gui"]
[workspace.package]
version = "3.4.0"
version = "3.4.1"
edition = "2024"
license = "MIT"
authors = ["Nils Pukropp <contact@narl.io>"]
+11
View File
@@ -11,7 +11,17 @@ scratch (user data in `staging/` and `recovery/` is never touched by this).
## [Unreleased]
## [3.4.1] — 2026-10-16
Schema: **42**, unchanged.
### Fixed
- **After a password reset, the drive never mounted and the app stayed on "Connecting…".** A
reset gives the account new keys, and Proton locks the Drive volume that was encrypted to the
old ones. The service then failed every start with `failed to decrypt: missing key`. It now
starts a new My Files volume, as the web app does. The files in the locked volume can still be
restored from [drive.proton.me](https://drive.proton.me) with the previous password
(B210, [#40](https://github.com/narrrl/proton-drive-linux/issues/40)).
- **A blocked sign-in said the app version was no longer supported.** Proton refuses sign-in for
a while after it suspects abuse, and its message then asks you to update. The app and
`pdfs login` now say that Proton is refusing sign-in for now and that waiting helps
@@ -1794,6 +1804,7 @@ First stable release: FUSE files-on-demand mount, sync daemon under `proton-driv
- The outstanding FUSE defects tracked in `docs/BUGS.md`, plus a truncate defect, validated
by a new POSIX compliance suite for the filesystem.
[3.4.1]: https://github.com/narrrl/proton-drive-linux/releases/tag/v3.4.1
[3.4.0]: https://github.com/narrrl/proton-drive-linux/releases/tag/v3.4.0
[3.3.0]: https://github.com/narrrl/proton-drive-linux/releases/tag/v3.3.0
[3.2.1]: https://github.com/narrrl/proton-drive-linux/releases/tag/v3.2.1
+1 -1
View File
@@ -9,7 +9,7 @@
# Build + install: cd packaging && makepkg -fi
pkgname=proton-drive-linux
pkgver=3.4.0
pkgver=3.4.1
pkgrel=1
pkgdesc="Unofficial Proton Drive client for Linux: files-on-demand FUSE mount, CLI, GTK4 app + tray"
arch=('x86_64')
+1 -1
View File
@@ -6,7 +6,7 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: proton-drive-linux 3.4.0\n"
"Project-Id-Version: proton-drive-linux 3.4.1\n"
"Report-Msgid-Bugs-To: https://github.com/narrrl/proton-drive-linux/issues\n"
"POT-Creation-Date: 2026-10-13 18:38+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"