Repository navigation
Limit CurseForge uploads to one attempt - #8
Merged
SkyBlade1978 merged 1 commit intoOct 27, 2026
Merged
SkyBlade1978 merged 1 commit into
SkyBlade1978 merged 1 commit into
Conversation
SkyBlade1978
merged commit Oct 27, 2026
2e50fe3
into
MinecraftModDevelopmentMods:master-1.10.2
5 checks passed
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.
CurseForge can return an HTTP 500 after accepting a file. The publisher's default two-attempt policy then submits the same file again, leaving a rejected duplicate alongside the valid upload.
Limit CurseForge publication to one attempt and document checking the project's file list and hash before any manual retry. Other publication stages are unchanged. This does not upload another file or change the released game jar.
Validation used the retry function from the pinned publisher revision: an accepted upload followed by HTTP 500 or timeout makes one call and surfaces the error; success also makes one call. A control using the previous default makes two calls and reproduces the duplicate request. The action metadata confirms this input is the total number of attempts.