Repository navigation
Stage the 1.13.2 release bundle correctly - #142
Merged
SkyBlade1978 merged 1 commit intoNov 15, 2026
Conversation
SkyBlade1978
merged commit Nov 15, 2026
f05f720
into
MinecraftModDevelopmentMods:master-1.13.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.
The first 1.13.2 release attempt stopped at bundle validation. CI had kept the build folders in the uploaded artifact, while the publisher expects the three jars, checksums and changelog together in one folder.
This stages that flat bundle before uploading it. The release checks stay as they are, and the game, sources and Javadoc jars are unchanged from the tested build. Nothing was published by the stopped attempt.