Aria2 Next: baixar versions anteriors

## Summary

Aria2 Next 3.0.5 fixes downloads from servers that answer a range request with a 206 but no usable Content-Range, and reports where redirects lead. Release assets cover the same seven platforms.

### Fixed

• A server that answers 206 without a Content-Range, or with one that places the body elsewhere, is now treated as a server that ignores ranges：the download continues on one connection from byte zero. Before, each answer was rejected and retried, so with `max-tries=0` a download from such a server (cloud.mail.ru, for example) stayed at 0% forever. The warning now includes the header the server sent ([rayburst#734](https://github.com/AnInsomniacy/rayburst/issues/734)).
• `aria2.getServers` reports the address a redirect leads to as `currentUri`, as aria2 does, instead of repeating the original URI ([rayburst#730](https://github.com/AnInsomniacy/rayburst/issues/730)).

### Downloads

| Platform | Download |
| --- | --- |
| Linux x86_64 | `aria2-next-3.0.5-linux-x86_64` |
| Linux ARM64 | `aria2-next-3.0.5-linux-aarch64` |
| macOS Apple Silicon | `aria2-next-3.0.5-macos-arm64` |
| macOS Intel | `aria2-next-3.0.5-macos-x86_64` |
| Windows x86_64 | `aria2-next-3.0.5-windows-x86_64.exe` |
| Windows ARM64 | `aria2-next-3.0.5-windows-arm64.exe` |
| Android ARM64 | `aria2-next-3.0.5-android-arm64` |
| Checksums | `aria2-next-3.0.5-checksums.sha256` |

## Summary
Aria2 Next 3.0.1 fixes regressions found in 3.0.0.
Linux builds no longer crash when BitTorrent starts, compressed subtitle tracks are readable again, and live global option changes now reach tasks that are already running.
Command line, configuration files and JSON-RPC are unchanged, and release assets cover the same seven platforms.

### Fixed
Linux: the engine no longer crashes with a segmentation fault as soon as the BitTorrent session starts https://github.com/AnInsomniacy/aria2-next/issues/65.
libtorrent was built as C++17 while the engine is C++20, so the two disagreed on the layout of shared Asio types; libtorrent now builds with the engine's standard.
Changing a live global option with aria2.changeGlobalOption, such as bt-first-last-piece-first or force-sequential, now applies to running tasks that inherit it, instead of only after they restart.

### Changed
--http-accept-gzip defaults to true again, as in 2.8.x.
Servers that compress subtitle tracks regardless of the request no longer leave them saved compressed and unparsable https://github.com/AnInsomniacy/aria2-next/issues/64.
Linux and macOS release builds, and CI, start a real BitTorrent session over RPC before assets are published.

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

| Platform | Asset |
| --- | --- |
| Linux x86_64 | `aria2-next-3.0.1-linux-x86_64` |
| Linux ARM64 | `aria2-next-3.0.1-linux-aarch64` |
| macOS Apple Silicon | `aria2-next-3.0.1-macos-arm64` |
| macOS Intel | `aria2-next-3.0.1-macos-x86_64` |
| Windows x86_64 | `aria2-next-3.0.1-windows-x86_64.exe` |
| Windows ARM64 | `aria2-next-3.0.1-windows-arm64.exe` |
| Android ARM64 | `aria2-next-3.0.1-android-arm64` |
| SHA-256 checksums | `aria2-next-3.0.1-checksums.sha256` |

### 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)

## Summary

Aria2 Next 2.7.0 improves HTTP/HTTPS range downloads, interrupted transfers, and paused stream recovery. It includes changes since the previous published release, v2.6.8. CLI and RPC callers can use the improvements without new configuration. Release targets remain Linux, macOS, Windows, and Android.

### Fixed

• Fixed multi-connection and resumed downloads failing on servers that reject ETag-based `If-Range` requests (#43). Requests now use `If-Match` with valid strong ETags, or `If-Unmodified-Since` with valid modification dates.
• Prevented malformed or weak ETags from being sent as strong validators. Explicit resource changes stop the transfer before different file versions can be combined.
• Added a bounded complete-download fallback when a server ignores byte ranges. Existing partial files remain protected unless `allow-overwrite` permits restarting from zero.
• Restored saved progress for paused HTTP/SFTP tasks after an engine restart, before network transfer resumes.
• Preserved the missing suffix of short partial responses and correctly handled empty HTTP files.
• Corrected libcurl completion-message handling and shutdown ordering while native socket callbacks remain active.

### Changed

• Delegated connection setup and low-speed timeouts to libcurl. Slow tail ranges are reassigned only when the remaining work justifies another request.
• Refined concurrency reduction and staggered retries for HTTP 403, 429, and 503 responses, while respecting server retry delays.
• Extended trace diagnostics with request queue time, connection reuse, and negotiated HTTP version.
• Expanded local HTTP transfer validation for conditional requests, range fallback, file-version changes, and paused restart. Validation uses local fixtures and checks completed file hashes.

### Downloads

Standalone executables and the SHA-256 checksum file are attached by the release workflow after successful builds.

| Platform | Asset |
| --- | --- |
| Linux x86_64 | `aria2-next-2.7.0-linux-x86_64` |
| Linux ARM64 | `aria2-next-2.7.0-linux-aarch64` |
| macOS Apple Silicon | `aria2-next-2.7.0-macos-arm64` |
| macOS Intel | `aria2-next-2.7.0-macos-x86_64` |
| Windows x86_64 | `aria2-next-2.7.0-windows-x86_64.exe` |
| Windows ARM64 | `aria2-next-2.7.0-windows-arm64.exe` |
| Android ARM64 | `aria2-next-2.7.0-android-arm64` |
| Checksums | `aria2-next-2.7.0-checksums.sha256` |

[Full changelog](https://github.com/AnInsomniacy/aria2-next/compare/v2.6.8...v2.7.0)

## Summary

This release improves Windows HTTPS and numeric IP handling, then completes the official release pipeline by automatically publishing Linux x86_64 and ARM64 container images after release assets are uploaded.

### Changed

Official GitHub Releases now dispatch Docker publishing for the exact release tag after every maintained binary and checksum has uploaded successfully.
Manual release validation remains build-only, while Docker Publish remains independently available for rebuilding the latest or a selected release.

### Fixed

WinTLS now tolerates unavailable certificate revocation services while preserving trust-chain, hostname, validity, and confirmed-revocation checks.
Numeric IPv4 and IPv6 parsing no longer depends on locally configured network interfaces.
Peer blocklist matching now handles IPv4-mapped IPv6 addresses consistently.

### Downloads

| Platform | Download |
| --- | --- |
| Linux x86_64 | `aria2-next-2.5.6-linux-x86_64` |
| Linux ARM64 | `aria2-next-2.5.6-linux-aarch64` |
| macOS Apple Silicon | `aria2-next-2.5.6-macos-arm64` |
| macOS Intel | `aria2-next-2.5.6-macos-x86_64` |
| Windows x86_64 | `aria2-next-2.5.6-windows-x86_64.exe` |
| Windows ARM64 | `aria2-next-2.5.6-windows-arm64.exe` |
| Android ARM64 | `aria2-next-2.5.6-android-arm64` |
| Checksums | `aria2-next-2.5.6-checksums.sha256` |

## Summary

This release fixes a Linux startup compatibility regression in the standalone aria2-next engine. It
removes the runtime dependency on the OpenSSL legacy provider for ARC4 handling, so packaged builds
can start in environments where OpenSSL provider modules are unavailable or hidden by AppImage and
sandbox runtime paths.

## Changed

- ARC4 encryption now uses aria2-next's internal implementation consistently instead of selecting an
OpenSSL, libgcrypt, or nettle backend at build time.
- Unused ARC4 backend source files were removed from the maintained CMake source inventory.

## Fixed

- Fixed engine startup failure on Linux systems where OSSL_PROVIDER_load("legacy") could not find
the OpenSSL legacy provider module.
- Fixed AppImage and distribution runtime compatibility for environments that do not expose
/usr/lib/ossl-modules to the bundled engine.