Update binaries to rclone v1.73.0

[github-actions]

User description

Automated Binary Update

This PR updates the bundled binaries:

• rclone: v1.72.1 → v1.73.0
• fusermount3: Updated from Termux packages
• inotifywait: Updated from Termux packages

Architectures Updated

• arm
• arm64
• x86
• x64

Changelog

See rclone releases for details.

---

This PR was automatically created by the update-binaries workflow.

---

PR Type

Enhancement

---

Description

• Update bundled rclone binaries to v1.73.0

• Refresh Git LFS pointers for all architectures

• Bump module version string accordingly

---

Diagram Walkthrough

flowchart LR
  rclonebin["rclone binaries (arm/arm64/x86/x64)"]
  lfs["Git LFS pointers updated"]
  moduleprop["`module.prop` version string"]
  rclonebin -- "new v1.73.0 artifacts" --> lfs
  lfs -- "reflect new release" --> moduleprop

Loading

File Walkthrough

	Relevant files
Dependencies	rclone Update arm rclone Git LFS pointer                                                common/binary/arm/rclone Update Git LFS oid to new binary Update Git LFS size for artifact +2/-2      rclone Update arm64 rclone Git LFS pointer                                            common/binary/arm64/rclone Update Git LFS oid to new binary Update Git LFS size for artifact +2/-2      rclone Update x64 rclone Git LFS pointer                                                common/binary/x64/rclone Update Git LFS oid to new binary Update Git LFS size for artifact +2/-2      rclone Update x86 rclone Git LFS pointer                                                common/binary/x86/rclone Update Git LFS oid to new binary Update Git LFS size for artifact +2/-2
Configuration changes	module.prop Bump module version to rclone v1.73.0                                        module.prop Bump version from rclone v1.72.1 to v1.73.0 +1/-1

---

[zam-review]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 Security concerns Supply chain risk: This PR updates bundled executable binaries via new Git LFS OIDs. Verify provenance (download/build source), confirm hashes against trusted release artifacts, and ensure the binaries are not tampered with before shipping. Consider documenting the upstream URLs/commit/tag used and the expected checksums for each architecture.

⚡ Recommended focus areas for review Binary Integrity Validate that the new Git LFS object points to the intended rclone v1.73.0 ARM binary (correct upstream source, expected build flags, and runnable on target devices). Also sanity-check the notably smaller binary size versus the previous version to ensure it wasn’t accidentally compressed/stripped incorrectly or replaced with an unexpected artifact. oid sha256:cf10cc846b307dbeacdbea91a4a1c57bba8af13e1828558af0eb8871eb31893e size 70189240 Arch Compatibility Confirm the ARM64 artifact is actually the correct architecture build and executes properly (e.g., rclone version reports v1.73.0), since this change only updates LFS pointers and does not inherently guarantee runtime compatibility on-device. oid sha256:f15f7056ced525da911a8277935760c9df349baacb6929401d5058791f540461 size 70451384 Versioning Ensure the version string update is consistent with the release being shipped and that other version metadata (e.g., versionCode policy) does not require a bump for distribution/update semantics in your packaging ecosystem. version=rclone: (v1.73.0) mod: (v1.15) versionCode=115

[zam-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Increment the module version code Bump versionCode when updating bundled binaries so module managers can detect and deliver the update reliably. Keeping versionCode unchanged may cause devices to skip installing this new rclone build. module.prop [3-4] version=rclone: (v1.73.0) mod: (v1.15) -versionCode=115 +versionCode=116 Suggestion importance[1-10]: 6 __ Why: The PR updates the bundled rclone binaries (and version=) but leaves versionCode=115 unchanged, which can prevent some module managers from recognizing the update. This is a reasonable release-management improvement, though not strictly a functional bug in the code itself.	Low