PDrive rclone v1.76.0-beta.10204.2

This PDrive-maintained rclone build updates the reviewed Proton Drive dependency used by PDrive Control Center. It is a project dependency build, not a general-purpose rclone release.

Changes since pdrive-v1.76.0-beta.10204.1:

• Retains the reviewed backend file-data bandwidth limiter.
• Integrates the bridge worker-drain fix tracked upstream in Proton-API-Bridge#8.
• Adds bounded retries for failed Proton block uploads with fresh upload links, while keeping client errors terminal.

Build provenance:

• Source commit: d83aeb8fcb82fea3c6d28003d47cab5a02e7f026
• Bridge commit: c059d7573afbc67d9a78e44db9b6aaac384c4263
• Built as a static Linux amd64 binary with Go 1.26.7 in a digest-pinned rootless container.
• Two independent clean builds were byte-identical.
• SHA-256: 85da18d19fd5e4a0969ed0fcc1ec43d00a90dfa7a06ce5483fd681c619db390d

Full comparison: pdrive-v1.76.0-beta.10204.1...pdrive-v1.76.0-beta.10204.2

PDrive rclone v1.76.0-beta.10204.1

PDrive-maintained rclone dependency for Proton Drive mounts.

This is not a general rclone release. It is the pinned binary used by proton-drive-linux while the changes are reviewed upstream.

Source:

• rclone base: v1.76.0-beta.10204.660144d31 (660144d311ef)
• PDrive data-only upload/download limiter: 73769e35cf9c
• source-pinned distribution commit: c81f9a3d15b9
• Proton API Bridge worker fix: a38695820cd0
• upstream bridge PR: rclone/Proton-API-Bridge#8

The backend-specific limiter caps aggregate file payload while leaving Proton API and metadata requests outside the limiter. The binary retains the exact pinned rclone version identity for VFS-cache compatibility; PDrive verifies the backend command rather than trusting the version string alone.

Built rootlessly with Go 1.26.7, CGO_ENABLED=0, -trimpath, and a static Linux amd64 target. The SHA-256 checksum is attached separately.