github AnInsomniacy/aria2-next v2.2.0
v2.2.0 - Core Modernization Cutover

latest releases: v3.0.4, v3.0.3, v3.0.2...
4 months ago

Caution

This is an aggressive core modernization release. It removes legacy protocol engines, legacy compatibility surfaces, and several old dependency backends. It may expose integration bugs and can make systems unstable. Test before using it as a production engine.

Summary

aria2-next 2.2.0 completes the core modernization track. Ordinary URL transfers now use libcurl, JSON-RPC transport uses Boost.Beast, JSON handling uses Boost.JSON, TLS and crypto are OpenSSL-centered, BitTorrent is libtorrent-only, and ED2K remains native with modern progress reporting. This release keeps the aria2-next executable and JSON-RPC workflow, but deliberately prunes obsolete backends and compatibility surfaces.

Added

  • libcurl-backed HTTP, HTTPS, FTP, FTPS, SFTP, and SCP transfer ownership.
  • Boost.Asio runtime foundation for modern library integration.
  • Boost.Beast JSON-RPC HTTP and WebSocket transport.
  • Boost.JSON request parsing and response serialization.
  • ED2K in-flight progress reporting through RPC for UI progress while verified bytes remain unchanged until validation.
  • libtorrent pause-after-metadata support for magnet file selection workflows.

Changed

  • Release packaging now builds the modern dependency closure around zlib, OpenSSL, libssh2-for-curl, curl 8.20.0, Boost, and libtorrent-rasterbar.
  • Release workflow validation now uses deterministic local transfer smoke tests instead of a fragile third-party public URL.
  • Windows x86_64 release builds now use the POSIX MinGW runtime needed by the C++17 and Boost.Asio path.
  • Windows runtime dependency checks now allow the system MSWSOCK.dll socket extension dependency.
  • Windows ARM64 release builds now pass absolute llvm-mingw tool paths through CMake.
  • Storage progress now separates verified completedLength from unverified inFlightCompletedLength.
  • Torrent file and magnet ingress now hand raw torrent data and metadata intent to libtorrent instead of keeping native BitTorrent fallback paths.
  • CMake dependency detection now expects the modern library set and reports the enabled feature surface at configure time.

Fixed

  • Restored libtorrent magnet pause-metadata=true semantics so metadata can resolve before selected payload downloading starts.
  • Preserved metadata-pause state across saved libtorrent progress data.
  • Fixed RPC progress gathering for file entries without a native bitfield.
  • Fixed ED2K build coverage around Kad command headers and Windows macro collisions.
  • Updated Android NDK release dependency metadata.

Breaking Changes

  • Native BitTorrent engine support is removed; BitTorrent is libtorrent-rasterbar only.
  • XML-RPC, Metalink, Metalink3, Metalink4, Expat, and libxml2 support are removed.
  • Legacy TLS and crypto backends are removed, including GnuTLS, WinTLS, nettle, libgcrypt, GMP, and internal fallback paths.
  • Native HTTP, FTP, SFTP, proxy, cookie, browser-cookie, auth, netrc, wslay WebSocket, and custom JSON parser ownership has been removed or replaced by the modern library owners.
  • The optional public C++ libaria2 API, examples, pkg-config file, install rules, and related docs are removed. JSON-RPC is the maintained control surface.
  • Removed stale options include follow-torrent, http-auth-challenge, ftp-reuse-connection, ssh-host-key-md, rpc-user, rpc-passwd, rpc-secure, rpc-certificate, and rpc-private-key.

Downloads

Platform Download
Linux x86_64 aria2-next-2.2.0-linux-x86_64
Linux ARM64 aria2-next-2.2.0-linux-aarch64
macOS Apple Silicon aria2-next-2.2.0-macos-arm64
macOS Intel aria2-next-2.2.0-macos-x86_64
Windows x86_64 aria2-next-2.2.0-windows-x86_64.exe
Windows ARM64 aria2-next-2.2.0-windows-arm64.exe
Checksums aria2-next-2.2.0-checksums.sha256

Don't miss a new aria2-next release

NewReleases is sending notifications on new releases.