Aquesta és una versió anterior. La versió actual és la 3.0.5. Aria2 Next 3.0.5 · Data de publicació:
Fitxers d’instal·lació 2.8.3
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | Portable | — | — | github.com | VirusTotal |
| ARM64 | Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
### 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:
| Platform | Asset |
| --- | --- |
| Linux x86_64 | `aria2-next-2.8.3-linux-x86_64` |
| Linux ARM64 | `aria2-next-2.8.3-linux-aarch64` |
| macOS Apple Silicon | `aria2-next-2.8.3-macos-arm64` |
| macOS Intel | `aria2-next-2.8.3-macos-x86_64` |
| Windows x86_64 | `aria2-next-2.8.3-windows-x86_64.exe` |
| Windows ARM64 | `aria2-next-2.8.3-windows-arm64.exe` |
| Android ARM64 | `aria2-next-2.8.3-android-arm64` |
| SHA-256 checksums | `aria2-next-2.8.3-checksums.sha256` |
Full changelog:[v2.8.2...v2.8.3](https://github.com/AnInsomniacy/aria2-next/compare/v2.8.2...v2.8.3)https://github.com/AnInsomniacy/aria2-next/releases/tag/v2.8.3