Skip to content

v0.1.14

Choose a tag to compare

View all tags
@ehstbr ehstbr released this 08 Aug 13:51
· 20 commits to main since this release
v0.1.14
ad28b86
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

PyNextCloud Sync 0.1.14

This release introduces a protected first-synchronization workflow and a persistent safety system designed to prevent unexpected local problems from propagating destructive changes to Nextcloud.

Released: August 8, 2026
Release type: Safety-focused update

Protected First Synchronization

The application no longer starts normal bidirectional synchronization immediately after connecting an account.

Instead, it creates a new private staging folder and downloads a fresh snapshot of the server tree. This prevents an old or unrelated .sync_*.db database in the selected local folder from being silently reused.

Before normal synchronization is enabled, the application analyzes and presents:

  • files available only on the computer;
  • files available only on Nextcloud;
  • identical files;
  • files with different contents;
  • file-versus-folder conflicts.

The user can review the result before any final merge is performed.

Conflict Handling

Four conflict-handling policies are now available:

  • preserve both versions, keeping the newest version at the original path;
  • give priority to the Nextcloud version;
  • give priority to the computer version;
  • review every conflict individually.

When one version is not selected as the primary file, it is preserved under a clearly identified dated filename instead of being silently discarded.

Safe Upgrade from Version 0.1.13

Existing installations upgraded from version 0.1.13 start in a paused state.

Automatic triggers, timers, inotify, notify_push, and nextcloudcmd remain disabled until the protected review is completed and a new verified safety baseline has been created.

This pause is intentional and prevents an existing installation from resuming bidirectional synchronization before its local and remote trees have been reviewed.

Existing synchronization databases are archived outside the synchronized tree. They are never silently deleted or reused during initialization.

Deletion Safety Guard

The application now maintains a persistent manifest of the last verified synchronization state.

Synchronization is blocked before nextcloudcmd starts when the configured local folder:

  • disappears;
  • becomes unreadable;
  • appears to have been replaced or remounted;
  • unexpectedly becomes empty;
  • loses its synchronization database;
  • suddenly loses too many previously synchronized files.

The user can then:

  • remain paused and investigate the problem;
  • restore the local tree from Nextcloud;
  • explicitly approve intentional deletions for one synchronization.

File-count and percentage thresholds can be configured in the application settings. Missing, replaced, empty, or unreadable folders always require review regardless of those thresholds.

Additional Improvements

  • Added warning states to the main window and tray menu.
  • Added desktop notifications for blocked synchronization.
  • Preserved the credential, GNOME integration, translation, low-memory interface, and Debian upgrade improvements from version 0.1.13.

Download and Installation

Download the .deb package attached to this release and run:

sudo apt install ./pynextcloud-sync_0.1.14_all.deb

After upgrading from 0.1.13, open the application and complete the protected initialization review before automatic synchronization can resume.

Release Files

  • pynextcloud-sync_0.1.14_all.deb — installation package for Debian, Ubuntu, and compatible distributions.
  • PyNextCloud-Sync-0.1.14.zip — complete source code.
  • PyNextCloud-Sync-0.1.14-changed-files.zip — the 34 files added or modified since version 0.1.13.

Validation

  • 89 automated tests passed.
  • First synchronization remains paused until the protected review is completed.
  • Existing synchronization databases are archived rather than reused or silently removed.
  • Safety conditions are evaluated before the bidirectional synchronization engine starts.

SHA-256

DEB:
89035f38697cea9f5b9f893ac6874573e9bf3a86497cf98d6426751fe35bffc3

Full source ZIP:
44ea61de72cb32ea531b54b3ec33d5e63d3d9faf5c535cbab73ac13ec2eceaaa

Changed-files ZIP:
9f5cac8cb81899956dd52de48638ed1a2e0c0d0b09c0629e7b074cd1ee2ba272
Assets 4
Loading