AnInsomniacy/aria2-next v2.8.3

v2.8.3 - Download Isolation and Filename Resolution

on GitHub

Breaking Changes

--continue no longer adopts an existing file solely because its name or size matches. Stream recovery requires the original task GID, URL, output path and valid saved ranges. Preserve the saved session and recovery database when resuming interrupted tasks. Re-adding the URL as a new task follows the configured collision policy: rename, fail, or explicitly overwrite an inactive file.

Summary

Aria2 Next 2.8.3 isolates concurrent downloads that resolve to the same filename and keeps recovery records tied to their owning tasks. It also adds a filename-resolution RPC for clients that need to preview names before creating a download.

Fixed

• Same-name downloads: check active task reservations when selecting an output path or automatic suffix. Explicit overwrite permission no longer bypasses another active task's reservation.
• Existing-file protection: use exclusive file creation for new outputs when overwrite is disabled, preventing a file created between path selection and opening from being truncated.
• Incorrect completion and resume: remove file-size-based adoption, which could treat an unrelated file as complete or append downloaded bytes to it. Restore progress only from matching task recovery data.
• Recovery isolation: remove recovery records by task GID during failures, restarts, media handoffs and cleanup, preventing one task from deleting another task's state merely because they share a path.

Added

• aria2.resolveFilename(url, contentDispositionBytes) returns a suggested basename using the engine's existing filename resolver. It accepts a URL and the original Content-Disposition header bytes, creates no task and makes no network request. Clients can detect support through filename-resolution in aria2.getVersion().downloadFeatures.

Downloads

The release workflow builds the following standalone executables and uploads SHA-256 checksums:

Full changelog: v2.8.2...v2.8.3