Update dependency Downloader to v5 - autoclosed#1237
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
8ac9450 to
ed3d8e8
Compare
c702d94 to
edd0c66
Compare
edd0c66 to
a3ff467
Compare
a3ff467 to
f116f19
Compare
f4f6291 to
b0d79b3
Compare
b0d79b3 to
82e10d6
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
3.3.4→5.8.0Release Notes
bezzad/Downloader (Downloader)
v5.8.0: version 5.8.0Fixed issue #226 (AOT downloads failing with HTTP 428): the real cause was that some CDNs (e.g. BunnyCDN) return 428 as a per-client concurrency throttle for parallel chunks, and error classification relied on Exception.Source, which is empty under AOT/trimming — making the 428 fatal only in AOT. Error retry-ability is now decided by exception type and HTTP status code, deterministically across JIT and AOT.
Retries now use exponential backoff with full jitter instead of a fixed delay, so chunks throttled together (428/429/503) disperse on retry instead of repeating the burst.
428 Precondition Required and transport-level HttpRequestExceptions (no HTTP status) are now treated as transient/retryable; permanent client errors (400/401/403/404) and 500/502 remain non-retryable.
Fixed issue #231 (follow-up): in environments where a TLS-inspecting proxy/antivirus breaks concurrent HTTPS connections, parallel/range chunk downloads failed (SEC_E_DECRYPT_FAILURE, "response ended prematurely", aborted sockets) even though a single sequential connection worked. The download service now automatically falls back to a single connection and completes the download instead of failing, when a multi-connection attempt fails with a transient transport error.
v5.6.0: version 5.6.0Full Changelog: bezzad/Downloader@v5.4.0...v5.6.0
v5.4.0: version 5.4.0Full Changelog: bezzad/Downloader@v5.3.0...v5.4.0
v5.3.0: version 5.3.0What's Changed
New Contributors
Full Changelog: bezzad/Downloader@v5.2.0...v5.3.0
v5.2.0: version 5.2.0Fixed issue #220: Some servers don't like the Range header and respond with errors like 403, 404 or 503. even though the file is perfectly downloadable with a normal request (no Range header).
Full Changelog: bezzad/Downloader@v5.1.1...v5.2.0
v5.1.1: version 5.1.1What's Changed
New Contributors
Full Changelog: bezzad/Downloader@v5.1.0...v5.1.1
v5.1.0: version 5.1.0What's Changed
Full Changelog: bezzad/Downloader@v5.0.0...v5.1.0
v5.0.0: version 5.0.0What's Changed
New Contributors
Full Changelog: bezzad/Downloader@v4.1.1...v5.0.0
v4.1.1: version 4.1.1What's Changed
New Contributors
Full Changelog: bezzad/Downloader@v4.0.3...v4.1.1
v4.1.0: version 4.1.0 pre-releaseWhat's Changed
New Contributors
Full Changelog: bezzad/Downloader@v4.0.3...v4.1.0
v4.0.3: version 4.0.3Add MinimumChunkSize to set minimum size a single chunk should have
v4.0.2: version 4.0.2Configuration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.