Repository navigation
Bypass cached Maven reads during release checks - #6
Merged
SkyBlade1978 merged 1 commit intoNov 5, 2026
Conversation
SkyBlade1978
merged commit Nov 5, 2026
fd53eda
into
MinecraftModDevelopmentMods:master-1.10.2
4 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.
Maven accepted the baseSteam upload, but the runner was still seeing a cached 404 from before the upload. The public jars are present and match CurseForge. I confirmed that a unique query parameter gets a fresh read of the same Maven URL. This applies to the preflight and verification reads, without changing upload URLs or weakening the byte checks.