Repository navigation
Releases
Nextcloud MyGo 0.1.3 (test build, installers not code-signed)
Test build. Nextcloud MyGo 0.1.3 for Windows 11, one per-user installer per
architecture: arm64 for Windows on Arm (native ARM64 only), x64 for x64 PCs. The
installers are not Authenticode-signed (there is no Windows code-signing certificate), so
Windows SmartScreen warns on the first install. Check each download against SHA256SUMS.
Installed copies update in the app (Settings, About & updates; off until you turn it on):
it reads update-windows-<arch>.json of the latest release and installs only an update archive
signed with the project's update key, through the same per-user installer.
Both packages were built and passed the fast test tier natively on GitHub's Windows x64 and
ARM64 runners, and every PE file in them passed the architecture check. The real-server test
tier runs outside GitHub Actions.
Licenses: Nextcloud MyGo is GPL-3.0. Nextcloud-MyGo-0.1.3-licenses.zip holds the
license texts of Nextcloud Desktop, Qt, OpenSSL, SQLite, zlib, QtKeychain, KArchive, libp11
and the Go modules, and SOURCE.txt names the corresponding source: this tag of the
repository, its third_party/nextcloud submodule and the patches in patches/nextcloud/.
In this version
Fixes and small features the user reported on 2026-11-15 after using 0.1.2.
- Setup creates the base folder. Adding folders failed when the base folder (
Nextcloudin your
user folder by default) did not exist yet: SyncD creates only the synced folder itself and needs its
parent. The interface now creates the parent first. - Warning before merging. When a chosen local folder already holds files, setup now stops once,
names it and says how syncing merges it with the server's (nothing is deleted; a different file of the
same name is kept as a conflict copy), with Merge and continue. - Several folders at once. Only the first of several chosen folders was added: SyncD announces the
new configuration revision in an event after it answers, so the nextfolders.addwent out with the
old revision and was refused (REVISION_CONFLICT), and setup stopped there.Remote.AddFoldernow
waits for the new revision and tries again with a fresh inspection, and setup adds every folder and
names any that failed. - In-app updates. No in-app update could install: the interface held SyncD at the update safe point
and the installer asked again, which SyncD refuses while one holds, so the installer gave up after two
minutes. The interface now stops SyncD at the safe point before it starts the installer, and starts it
again if the installer refuses. - Installer. Setup and the uninstaller are windows instead of consoles: icon, version, Install or
Remove, progress and the result, with version details and a manifest on both executables
(packaging). The installer is now
Nextcloud-MyGo-<version>-<arch>-setup.exe;-quietkeeps the console behavior for scripts. - How a folder keeps its files. An on-demand folder's menu offers Always keep on this PC, On demand
and Free up space, and a full-file folder's offers Use on-demand files (converted in place, nothing
downloaded again) (on-demand). Explorer offers "Always keep on this device"
and "Free up space" only inside a synced folder, not on the sidebar entry's base folder. - Never elevated. The 0.1.2 setup had no manifest, so Windows' installer detection elevated it and
the app it started then ran as administrator, against the rule that it never does. The 0.1.3
installer runs as the invoking user (asInvoker), refuses to run as administrator, and refuses before
closing anything when the running app is elevated: quit it from the tray first. An elevated SyncD
also made the lease checks of a second, normal SyncD on the same machine refuse every folder below a
shared parent (FOLDER_OWNED), which is how this was found. - Renaming an address. Every approved address, the main one too, can be renamed and given its kind.
- Tests. Real-daemon tests remove their profile bottom-up, as setup does:
os.RemoveAllfails with
"too many levels of symbolic links" belowAppData\Localon the ARM64 test machine (build 26300),
where every profile had been left behind; CI had not shown it.
Protocol 1.12 (folders.setAvailability, the folder's availability, endpoints.rename) and Control
schema 13 (accounts.main_name, accounts.main_kind). Versions, checked 2026-11-15, unchanged: Go 1.27.4,
MyGo v0.9.1, Nextcloud Desktop v35.0.3 (engine; the 23 upstream patches, fingerprint CF0C68C10DD7),
Nextcloud servers 35.0.3 and 34.0.6 for tests.
Nextcloud MyGo 0.1.2 (test build, installers not code-signed)
Test build. Nextcloud MyGo 0.1.2 for Windows 11, one per-user installer per
architecture: arm64 for Windows on Arm (native ARM64 only), x64 for x64 PCs. The
installers are not Authenticode-signed (there is no Windows code-signing certificate), so
Windows SmartScreen warns on the first install. Check each download against SHA256SUMS.
Installed copies update in the app (Settings, About & updates; off until you turn it on):
it reads update-windows-<arch>.json of the latest release and installs only an update archive
signed with the project's update key, through the same per-user installer.
Both packages were built and passed the fast test tier natively on GitHub's Windows x64 and
ARM64 runners, and every PE file in them passed the architecture check. The real-server test
tier runs outside GitHub Actions.
Licenses: Nextcloud MyGo is GPL-3.0. Nextcloud-MyGo-0.1.2-licenses.zip holds the
license texts of Nextcloud Desktop, Qt, OpenSSL, SQLite, zlib, QtKeychain, KArchive, libp11
and the Go modules, and SOURCE.txt names the corresponding source: this tag of the
repository, its third_party/nextcloud submodule and the patches in patches/nextcloud/.
In this version
One Explorer entry instead of one per folder, by the user's request of 2026-11-15.
- Explorer. On-demand folders now share one navigation pane entry per folder that holds them. With
setup's layout that is a single entry, "Nextcloud MyGo", which opens the base folder (Nextcloudin
your user folder by default). A folder elsewhere gets an entry for the folder that holds it, named
"Nextcloud MyGo - "; a folder that maps the whole account, or sits directly on a drive,
keeps an entry of its own. The 0.1.1 per-folder entries are removed when SyncD next starts each folder.
The entry goes when the last folder that uses it is removed; the uninstaller keeps an entry another
profile's folder still uses (on-demand). - Tests. The real-pipe tests give every pipe write a deadline and the
--versionprobe a timeout,
and the tier log keeps the names of tests running when Go's package timeout fires: the v0.1.1
release run had hung in one of them on ARM64 without saying which.
Known limitations: as for 0.1.1. Not yet verified: the shared entry as Explorer shows it, and an
upgrade from an installed 0.1.1 with the shipped installers.
Versions, checked 2026-11-15: MyGo moved to v0.9.1 (a patch release, no UI migration needed);
unchanged: Nextcloud Desktop v35.0.3 (engine), Nextcloud servers 35.0.3 and 34.0.6 for tests, Go 1.27.4.
Protocol 1.11, Control schema 12 and the 23 upstream patches (fingerprint CF0C68C10DD7) are unchanged.
Nextcloud MyGo 0.1.1 (test build, installers not code-signed)
Test build. Nextcloud MyGo 0.1.1 for Windows 11, one per-user installer per
architecture: arm64 for Windows on Arm (native ARM64 only), x64 for x64 PCs. The
installers are not Authenticode-signed (there is no Windows code-signing certificate), so
Windows SmartScreen warns on the first install. Check each download against SHA256SUMS.
Installed copies update in the app (Settings, About & updates; off until you turn it on):
it reads update-windows-<arch>.json of the latest release and installs only an update archive
signed with the project's update key, through the same per-user installer.
Both packages were built and passed the fast test tier natively on GitHub's Windows x64 and
ARM64 runners, and every PE file in them passed the architecture check. The real-server test
tier runs outside GitHub Actions.
Licenses: Nextcloud MyGo is GPL-3.0. Nextcloud-MyGo-0.1.1-licenses.zip holds the
license texts of Nextcloud Desktop, Qt, OpenSSL, SQLite, zlib, QtKeychain, KArchive, libp11
and the Go modules, and SOURCE.txt names the corresponding source: this tag of the
repository, its third_party/nextcloud submodule and the patches in patches/nextcloud/.
In this version
On-demand files for Windows, by the user's decisions of 2026-11-14.
- On-demand files. Folders keep every remote file as a placeholder that downloads when an
application opens it (Windows Cloud Files). New folders default to on demand; full files stay
selectable. The capability is on where Cloud Files runs. - Folders added by 0.1.0 switch once, automatically. SyncD turns their files into in-sync
placeholders when it starts, without downloading, deleting or uploading anything and without
writing the journal: files that changed since their last sync and files it cannot open
stay ordinary until the first cycle makes them placeholders, and a folder that cannot switch (inside
a folder another app syncs, on a network drive) keeps full files and tries again at every start. The
folder's row says what happened or why not. - Explorer. Each on-demand folder has a navigation pane entry named "Nextcloud MyGo - ",
and the sync roots show the Nextcloud icon. - Uninstall releases on-demand folders first. Downloaded files become ordinary files, online-only
placeholders are deleted locally (the server keeps them), and nothing is removed if a folder cannot be
released. Full-file folders, journals, accounts and settings stay. - Two fixes found by acceptance. A local deletion in an on-demand folder never reached the server (the folder stayed in
SYNC_FAILED): patch 0020 lets SyncD carry upstream's restart flag between cycles, and a restarted cycle is no failure. An ordinary sparse file was read as an online-only placeholder and was deleted locally or not uploaded: patch 0021 requires the placeholder's recall flag, and sparse files convert like any other (on-demand). - First-cycle race. While an on-demand folder's first cycle runs, another process can ask Cloud Files for the directory listing; the listing creates the placeholders first and the cycle used to end as
SYNC_FAILED. SyncD now recognizes this (the placeholder holds the same server file ID) and reports a restarted cycle, excused once in a row (on-demand). - Same-second ETag handled. Nextcloud 35.0.3 can keep a file's ETag when it is rewritten twice within one second, so a file also edited locally could replace newer server content. Patch 0022 treats a different server size under an equal ETag as a server change: the file is downloaded, or becomes a conflict copy when it was also edited locally. Still undetectable: a same-size rewrite within one second, and a rewrite on a server whose parent folder also keeps its ETag (on-demand).
- Listing identity. Patch 0023 stores the file identity of placeholders created by the Cloud Files listing exactly, without the bytes read past the buffer (upstream).
- Protocol 1.11 and Control schema 12 (the conversion state of each folder). Upstream patches 0020 to 0023 added (23 in all, fingerprint
CF0C68C10DD7).
Known limitations:
- Downgrade: 0.1.0 refuses a schema 12 database. Remove the folders in 0.1.1 first, then reinstall 0.1.0.
- Uninstall handles only the running profile, and a Windows registration with no folder behind it (for
example after the Control DB was lost) blocks it, with no remedy in the app yet. - Thumbnails and lock or share overlays in Explorer need upstream's shell extension, which is not
built. - Not yet verified: the shipped installers and executables against a server (installing over a real
0.1.0, the uninstaller's release of on-demand folders); SyncD's own navigation entry and icon in Explorer;
behavior where Cloud Files is unavailable; conversion timing at 10,000 and 100,000 files in the real
daemon (platform notes). - The 0.1.0 limitations otherwise remain.
Versions, checked 2026-11-14 and unchanged: Nextcloud Desktop v35.0.3 (engine), Nextcloud servers
35.0.3 and 34.0.6 for tests; Go 1.27.4; MyGo v0.9.0. Qt and OpenSSL as recorded in build-lock.json.
Nextcloud MyGo 0.1.0 (test build, installers not code-signed)
Test build. Nextcloud MyGo 0.1.0 for Windows 11, one per-user installer per
architecture: arm64 for Windows on Arm (native ARM64 only), x64 for x64 PCs. The
installers are not Authenticode-signed (there is no Windows code-signing certificate), so
Windows SmartScreen warns on the first install. Check each download against SHA256SUMS.
Installed copies update in the app (Settings, About & updates; off until you turn it on):
it reads update-windows-<arch>.json of the latest release and installs only an update archive
signed with the project's update key, through the same per-user installer.
Both packages were built and passed the fast test tier natively on GitHub's Windows x64 and
ARM64 runners, and every PE file in them passed the architecture check. The real-server test
tier runs outside GitHub Actions.
Licenses: Nextcloud MyGo is GPL-3.0. Nextcloud-MyGo-0.1.0-licenses.zip holds the
license texts of Nextcloud Desktop, Qt, OpenSSL, SQLite, zlib, QtKeychain, KArchive, libp11
and the Go modules, and SOURCE.txt names the corresponding source: this tag of the
repository, its third_party/nextcloud submodule and the patches in patches/nextcloud/.
In this version
The first release: a test build for Windows 11, one per-user installer per architecture (x64 and
native ARM64).
- One account, several addresses. Each account can have several trusted addresses of the same
server (internet, home network, VPN). An address serves the account only after its server, its
TLS certificate and its folder namespace are verified. SyncD picks the address automatically, or
keeps the one you fix, and switches only between sync cycles, all folders of the account together.
A sign-in or certificate failure blocks an address; no score overrides it. - The Nextcloud Desktop engine. Discovery, reconcile, propagation and the journal are upstream
Nextcloud Desktop's, with 19 small patches, in SyncD, a background process of the current user.
The interface (Go and MyGo) talks to it over a local Named Pipe, protocol 1.10; closing the
window never stops sync. - File safety. Deletion protection holds large or unusual deletions for your review. An
unconfirmed upload, move or deletion is recovered by rediscovery; an unreachable server or an
unreadable folder never reads as empty. A modification cut mid-transfer leaves the server's
previous version in place (it is sent as a chunked upload). A local rename whose move fails on
the network stays renamed and is sent again. - Several accounts, each with several folders; signing in through the browser; renewal and
revocation of the app password; a full server or a slow one each reported as such. - The interface: Overview, Accounts & folders, Network, Activity with the deletion review,
Settings, the tray and its flyout; English and Simplified Chinese. - Installation and updates: per-user installers that upgrade in place and check that every
binary matches the architecture. In-app updates install only an archive signed with the
project's update key; they are off until turned on in Settings.
Known limitations:
- On-demand files are built but not offered (
virtualFiles). - The installers are not Authenticode-signed, so Windows SmartScreen warns on the first install.
- Tested on one native ARM64 machine. x64 binaries passed their tests under emulation there; the x64
installer has not run on x64 hardware. - Not shown: a real sleep and resume (simulated only), a 24-hour run (replaced by a 1-hour
accelerated soak), strict VPN egress, a second Windows session or user, end-to-end encrypted
folders, drive-letter reuse by another volume, and a journal restored by hand. Start at sign-in
is checked after the release. - Deletion protection counts each sync cycle on its own: deletions spread over several cycles are
not added up. - A safety block (a changed certificate, a server that is not the expected one) stays until SyncD
restarts. - On the test machine, Windows Credential Manager lost updates when several processes wrote to it
at the same moment. SyncD's own writes never overlap, but another program writing at that moment
could make an account ask you to sign in again. - One access violation in SyncD during a 20-minute test run was not reproduced in about five hours
of later runs and is not explained. - macOS is not part of this release.
Versions: Nextcloud Desktop v35.0.3 (engine), tested against Nextcloud server 35.0.3, 35.0.2 and
the previous major 34.0.6; Go 1.27.4; MyGo v0.9.0; Qt 6.12.0; OpenSSL 3.6.5.