TorrentNG main-20261013-2

User-facing changes

Added

• Desktop: TorrentNG Desktop is a new native app for Linux, macOS, and Windows. It runs the bundled engine locally or connects to a TorrentNG server, with a lightweight table and the same look as the WebUI.
• Webui: Settings > Appearance now offers browser-local regional date, time, and number formatting. Existing locale-aware displays use the selected region; interface text remains English.
• Webui: TorrentNG now lets each browser choose an interface language. Navigation, language settings, and the Add Torrent dialog use translated labels and intake guidance in twelve locales with English fallback. Torrent names, URLs, and paths remain unchanged; Arabic translated labels carry local right-to-left metadata while the rest of the app stays English and left-to-right.

Changed

• Webui: Torrent sizes, ratios, progress, storage usage, and speeds now use the selected regional number format. Arabic shell labels use local right-to-left metadata while untranslated workflows remain English and left-to-right.

TorrentNG main-20261013-1

User-facing changes

Added

• Settings: The TorrentNG GitHub repository now has a Sponsor button with Ko-fi as an option for users who want to support project maintenance.
• Webui: The login screen now links to first-login instructions for Docker, Linux packages, Kubernetes, existing-client deployments, Unraid, and YunoHost.
• Webui: The login screen now links Unraid users directly to the login guide, including how to open the container Console and retrieve their WebUI credentials.

Changed

• Deployment: The Engine quick start now creates its download volume automatically and loads the generated API token from the private .env file, so setup needs one fewer manual step.
• Authentication: Unraid login instructions now show how to open the TorrentNG container Console, retrieve the active WebUI credentials, and distinguish them from credentials used to connect qBittorrent or another backend.

Security

• Network: Quinn protocol dependencies now use quinn-proto 0.11.19, which includes upstream fixes for remote peer denial-of-service issues. No configuration change is required.
• Validation: Local test runs now require a trusted Linux sandbox that hides operator files, ambient secrets, service sockets, and network access from candidate test code. Dependency roots that resolve outside the candidate tree are rejected before they can be mounted into the sandbox.
  • Action required: run local tests through trusted launcher
• Validation: Validation task and runtime-probe processes now use restricted environment variables and private temporary settings, reducing exposure of unrelated credentials and configuration during validation.
• Ci Security: Local validation snapshots exclude dotted and extensionless credentials, private/API keys, access/refresh-token and client-secret material, suffixed dotenv credentials, and non-source files under credential folders. Source modules such as TokenStore.ts and safe templates such as tokens.env.example remain available; output logs have a visible truncation marker.
• Ci Security: Pull request validation now uses GitHub-hosted runners for every author. Persistent local runners are reserved for main-branch validation, reducing exposure of local services and files to proposed changes.
• Ci Security: Local validation excludes credential files and non-source files in credential-named folders while retaining source files such as auth.rs and token.js.

TorrentNG main-20261003-2

User-facing changes

Added

• Webui: Large torrent lists now show the visible row range and let you jump directly to a row number, so you can navigate distant entries without loading every row first.

Changed

• Webui: The Help dialog and status bar now offer Ko-fi as the only donation link, removing PayPal from the TorrentNG interface.

Fixed

• Packaging: Arch package publishing now stages every file named by its source recipe, so AUR updates include the build configuration and avoid missing-source failures.

TorrentNG main-20261001-5

User-facing changes

Added

• Crash Recovery: TorrentNG now records completion durability and detects unclean restarts, with configurable recovery and verification policies for download paths.
  • Action required: Review the crash-safety options in Settings or the configuration guide to choose durability and verification policies for your storage.

Security

• Authentication: Breaking: Fresh installs and upgrades without an explicit auth.password now use a unique, private WebUI password instead of a shared default. Configured API tokens work in either login field, and credentials remain configurable in Security settings. The native auth-token command writes credentials only to the controlling terminal and refuses redirected or non-interactive output.
  • Action required: Run torrentngd auth-token interactively; use torrentng auth-token for the compatibility service. Replace explicitly configured shared passwords.
• Authentication: Breaking: The compatible-client auth-token command now writes credentials only to the controlling terminal. It fails without an interactive terminal, so stdout redirection and pipelines cannot capture credentials.
  • Action required: Run torrentng auth-token from an interactive terminal.

TorrentNG YunoHost bundle yunohost-0.1.0-1

Portable TorrentNG binaries and WebUI assets for the YunoHost app package. This release does not publish the general TorrentNG release channels.

TorrentNG main-20261001-4

User-facing changes

Added

• Auth: Release builds include configurable WebUI username and password settings. Fresh loopback installs accept torrentng / torrentng; API tokens continue to work in either login field. Public-bind Unraid installs use API-token sign-in first, then can set a unique password.
  • Action required: Change the default WebUI credentials after first sign-in.

main-20261001-3

The universal torrent client interface: one WebUI/API for the TorrentNG Engine and qBittorrent, rTorrent, Transmission, and Deluge. Released from GitLab pipeline https://gitlab.home/keith/TorrentNG/-/pipelines/229

main-20261001-1

The universal torrent client interface: one WebUI/API for the TorrentNG Engine and qBittorrent, rTorrent, Transmission, and Deluge. Released from GitLab pipeline https://gitlab.home/keith/TorrentNG/-/pipelines/223

TorrentNG main-20260930-4

User-facing changes

Fixed

• Unraid: Unraid installation guidance now focuses on template selection, storage permissions, backend setup, and support. Repository submission and template maintenance instructions have moved to a maintainer guide.
• Sidecar: rTorrent log recovery is now recorded consistently when a previously missing log file appears, including on Windows. Persisted error state no longer depends on whether the path can be canonicalized.
• Storage: Windows file and directory moves now complete through pinned storage paths, and an interrupted directory delete reports when removal was only partial so operators can recover safely.

Security

• Containers: The native Engine container now uses Alpine 3.24 with a musl-linked daemon, replacing Debian runtime packages that triggered high severity container scan findings.

TorrentNG main-20260925-7

User-facing changes

Fixed

• Container: Compatible-client images now assign the cache database in /var/lib/torrentng to the selected PUID/PGID before opening it, so Unraid and Compose volumes created by older root-running images start without a manual ownership change.