AnInsomniacy/aria2-next v2.4.0

v2.4.0 - Stable Engine Baseline Restoration

on GitHub

Breaking Changes

Aria2 Next 2.4.0 intentionally restores the stable engine baseline from v2.1.4. The newer engine modernization work from the v2.2.x and v2.3.x series has been moved out of the stable line and will continue separately on the preview/engine-modernization branch.

Users depending on v2.2.x or v2.3.x-only behavior should test before upgrading. The stable channel now prioritizes the proven v2.1.4-compatible engine behavior while the modernized engine receives more validation.

Summary

This release re-aligns main with the proven v2.1.4 engine baseline and publishes it as v2.4.0.

The v2.2.x and v2.3.x modernization series introduced important architectural work, but it also changed too much of the engine surface too quickly. Some users hit regressions in real integrations, especially around HTTP transfer behavior, DNS resolution, logging, and download engine scheduling.

Sorry for the disruption this caused. The stable line should be predictable first. The modernization work will continue on preview/engine-modernization until it has enough real-world validation to return safely.

Changed

• The stable branch now uses the v2.1.4 engine implementation as the release baseline.
• The libcurl, libtorrent, Beast, Boost.JSON, spdlog, DNS policy, torrent metadata, and rate scheduling modernization changes from the v2.2.x and v2.3.x line are no longer part of the stable channel.

Fixed

• Restored the previously validated engine behavior used before the modernization series.
• Reduced stable-channel risk for users affected by regressions introduced during the v2.2.x and v2.3.x engine transition.

Downloads