Repository navigation
TaskOrbit v0.1.6
TaskOrbit 0.1.6 — transparent Mercury identity
- Smaller sidebar wordmark, with a compact 160 px footprint.
- Transparent Mercury wordmarks switch lettering for light and dark themes, without a black background.
- README presentation includes centered branding, badges, feature/download tables and actual application previews in four documentation languages.
- Instance administrator can check official releases and perform a one-click server upgrade with the optional updater container.
- Database backup and integrity verification precede replacement; failed health checks restore the previous server and database. Interrupted upgrades use a persistent recovery journal.
- Windows/macOS/Linux clients include a signed updater and a menu for returning to the local connection screen. Clients before 0.1.3 need one manual installation; 0.1.3 clients can use the in-app updater.
- Android checks newer releases and opens the persistent-key-signed APK for user-approved installation.
- Web/iPhone PWA detects a changed server version and offers reload after saving unfinished work.
- Mercury identity throughout the application; English main README and separate Persian, Arabic and Simplified Chinese README files.
- Independent TaskOrbit product descriptions across project documentation.
Downloads
Windows x64 installer; macOS Intel and Apple Silicon DMGs; Linux x64 DEB/AppImage; Android arm64 APK; web/server archive. Desktop updater packages and signatures, latest.json and SHA256SUMS accompany them. Server image: ghcr.io/sajadjanat/taskorbit:v0.1.6 and :stable, Linux amd64/arm64. See update guide.
Preview limitations
TaskOrbit remains an early preview with additional workflows on the roadmap. Installer builds do not establish physical-device installation or native server-connection verification. Windows/macOS OS code signing and macOS notarization are not configured; updater signatures are configured. Android is an APK without a Play Store listing. iPhone uses PWA without an App Store binary. Editing requires connectivity and private work data is not cached by the service worker. No production deployment is implied. See roadmap and verification.