-
JellyTau v0.13.3
Stable🏗️ Build and Test JellyTau / Run Tests (push) Skipped🏗️ Build and Test JellyTau / Android Compile Check (push) Skipped🏗️ Build and Test JellyTau / Supply Chain (push) Successful in 3m57s📱 Test APK / Build test APK (push) Successful in 20m27sPublish Documentation / Build & publish docs to gitea-pages (push) Successful in 3m45sTraceability Validation / Check Requirement Traces (push) Successful in 11sBuild & Release / Run Tests (push) Successful in 10m38sBuild & Release / Build Linux (push) Successful in 14m21sBuild & Release / Build Windows (push) Successful in 10m47sBuild & Release / Build Android (push) Successful in 20m26sBuild & Release / Create Release (push) Successful in 43sreleased this
2026-09-24 11:40:35 +00:00 | 0 commits to master since this release🐛 Fixes
- Coming back to the app no longer replaces the page with "Failed to load
item". After a few minutes in the background, resuming the app on a series
page could swap the whole page for that error, and it stayed until you
navigated away. The page refreshes itself on resume; a refresh that fails now
leaves what you were looking at on screen, and the error clears as soon as a
load succeeds. When a page genuinely cannot open, it now says why instead of
the generic message. (DR-297)
Downloads
Platform File Linux (portable) *.AppImage—chmod +xand runLinux (Debian/Ubuntu) *.deb—sudo dpkg -iLinux (Fedora/openSUSE) *.rpm—sudo rpm -iWindows *-setup.exe(NSIS). Unsigned — SmartScreen may warn on first run.Android *.apksideload, or*.aabfor Play ConsoleDesktop builds check for updates from here and can install a new
version in place, verifying its signature first.Verifying your download
sha256sum -c SHA256SUMSSHA256SUMScovers every file in this release. An SBOM
(*.cdx.json,frontend-dependencies.txt) lists what went into it.Requirements
- Linux: 64-bit, GLIBC 2.29+
- Windows: 64-bit Windows 10 or later
- Android: 8.0 or later, ~50 MB free
Report a problem: https://gitea.tourolle.paris/dtourolle/jellytau/issues
Downloads
- Coming back to the app no longer replaces the page with "Failed to load