Repository navigation
Releases: yava-code/OnlyDrive
Releases · yava-code/OnlyDrive
Release list
v0.1.4
Native mounts on macOS and Linux
gd mount now works beyond Windows: each account mounts natively at
~/.gd/mnt/<account> (no drive letters needed there).
- macOS uses rclone's built-in NFS backend, no macFUSE required; VFS
caching is enabled so the mount is writable - Linux uses the kernel FUSE backend (fuse3/kio-fuse, no root)
- autostart re-mounts at the same paths, the panel and the union mount
follow the same rules, doctor probes the backend with a live
round-trip and gives per-OS hints
OAuth migration toolkit for the 2026 client_id retirement
gd oauth setup: a walkthrough that opens the exact Google Cloud
Console pages (project, Drive API, consent screen, Desktop-app
credentials), stores the pair and re-authorizes every account; the
consent-screen step explains why the app must be published to
Production (unpublished apps lose refresh tokens every 7 days)gd reauth --all: batch re-authorization, one Allow click per account- doctor,
gd oauth show, usage, wizard and docs now point at the
walkthrough first
Changelog
- c44b065 linux: first-class native mounts via the FUSE backend
- d258deb ci: resolve the rclone path for the smoke, fail loudly when required
- c0a93e8 smoke: pre-create the first mountpoint for the FUSE backend
- 574beea mount: request the nfsmount backend explicitly on macOS
- aabfd16 mount: enable VFS caching for macOS NFS mounts
- f1e9488 mount: pass VFS cache mode through vfsOpt for macOS NFS mounts
- 24de5a1 oauth: guided setup walkthrough and batch re-auth
- 12f3312 release: v0.1.4
v0.1.3
Own Google client_id
rclone retires its shared Google Drive OAuth client during 2026. gd now
supports bringing your own, a one-time setup:
gd oauth set <client_id> <client_secret>
gd reauth acc1
gd oauth set|show|clear: store, inspect (secret masked) and remove your
own OAuth pair; the setup wizard asks about it for new accounts- every authorize and re-auth path, including the panel's add-account flow,
uses the stored client automatically GD_CLIENT_IDandGD_CLIENT_SECREToverride the stored pair (scripts, CI)gd doctorflags accounts still on the shared client and links the how-to;
the panel shows which client is in effect
Other
- version bump to 0.1.3 so existing installs see the update through
gd update - docs: README section "Own Google client_id", landing FAQ updated
Changelog
- bc52dec Foundation for own Google OAuth client_id
- 7e1b4bb gd oauth set/show/clear and wizard prompt for own OAuth client
- 60294f5 gd doctor: check for own Google OAuth client
- c1e4b56 Panel shows which Google OAuth client is in effect
- a0b2411 Prune dead wrappers from the OAuth feature
- 5063226 Docs: own Google client_id is supported, not just planned
- e3c0097 Add Apache-2.0 LICENSE
- 0423b0a release: v0.1.3
v0.1.2
Changelog
v0.1.1
Changelog
- 777b312 Add OnlyDrive landing page for GitHub Pages
- b945385 Fix cross-platform build: mirror Callbacks on non-Windows, stub deleteTask
- 0bb3f53 pages: fix mobile layout and tap targets
- 28295f0 pages: let configure-pages enable Pages on the repo
- d84dff7 v0.1.1: tray autostart, masked screenshots, app icons, direct download
v0.1.0
Changelog
- 86a486e Point installers at yava-code/OnlyDrive, ship trimmed header logo
- 4287c75 ci: run release job on v* tags
- c1ab135 gd v0.1.0: Google Drive as a local disk, MCP server, S3 endpoint, web panel
- ac0b7ef goreleaser: dedupe release artifacts by build id
- 3531393 webui: editorial redesign with OnlyDrive logo, quota meters, doctor drawer