resolve occasional 404 errors during release download #18
Conversation
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
The current implementation can sometimes cause a 404 error when
downloading release files immediately after a new release is created.
This happens because the release file upload is not yet complete when
the new release is initially created, leading to a download failure if
accessed too early. To ensure successful downloads, the new release is
now initially set as a prerelease until the release files have finished
uploading.
This issue was detected in my development environment around
Nov 7, 7:01:04 am (UTC), resulting in the following error:
```
$ rv ruby install 3.4.7
Error: InstallError(DownloadFailed { url: "https://github.com/spinel-coop/rv-ruby/releases/latest/download/ruby-3.4.7.arm64_sonoma.tar.gz", status: 404, body: "Not Found" })
```
The reason for using prerelease instead of draft is that the
GitHubReleases::upload_bottles used by brew rv-upload does not yet
support draft releases.
Collaborator
|
Hah, we had the exact same issue in my dayjob. Let me take a look at this... |
adamchalmers
approved these changes
Nov 8, 2025
Member
|
Great catch, thanks for the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
The current implementation can sometimes cause a 404 error when downloading release files immediately after a new release is created. This happens because the release file upload is not yet complete when the new release is initially created, leading to a download failure if accessed too early. To ensure successful downloads, the new release is now initially set as a prerelease until the release files have finished uploading.
This issue was detected in my development environment around Nov 7, 7:01:04 am (UTC), resulting in the following error:
The reason for using prerelease instead of draft is that the GitHubReleases::upload_bottles used by brew rv-upload does not yet support draft releases.