AnInsomniacy/aria2-next v2.6.4

v2.6.4 - Native TLS Trust and Leaner Delivery

on GitHub

Summary

Aria2 Next 2.6.4 restores automatic HTTPS certificate trust for portable Linux and Android builds, keeps native trust integration on Windows and macOS, and simplifies continuous delivery without reducing release coverage. Standalone binaries remain available for every maintained platform.

Added

• Added an offline build-time guard that verifies each libcurl build uses the intended platform trust backend and does not embed build-runner certificate paths.

Changed

• Windows continues to use Schannel and the Windows certificate store, while macOS continues to use Apple SecTrust.
• Linux and Android now use OpenSSL default trust paths and honor SSL_CERT_FILE and SSL_CERT_DIR without requiring a routine --ca-certificate override.
• Stream connection settings are normalized to the supported range before configuring libcurl task and session limits.
• Daily CI now runs one authoritative validation, build, and test job; release packaging remains isolated to official releases.
• Release publications can no longer cancel an active publication, and container registry permissions are limited to image publishing jobs.

Fixed

• Fixed native Linux dependency builds being misclassified as cross-compilation, which disabled libcurl CA discovery and caused valid HTTPS downloads to fail unless a CA file was supplied manually.
• Prevented platform builds from inheriting certificate paths from the GitHub build runner.
• Removed duplicate release packaging from pull-request and push validation while preserving all release targets, runtime dependency checks, checksums, and Docker publishing.

Downloads