Repository navigation
Fix prepared Forge 1.14 release publication - #147
Merged
SkyBlade1978 merged 1 commit intoOct 9, 2026
Merged
SkyBlade1978 merged 1 commit into
SkyBlade1978 merged 1 commit into
Conversation
SkyBlade1978
merged commit Oct 9, 2026
749296d
into
MinecraftModDevelopmentMods:master-1.14
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
1 participant
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.
What changed
Fix the prepared-release Maven path introduced by the Forge 1.14 build-script split. The first release attempt stopped during Gradle configuration because the publishing script could not access the expected jar filenames; no Maven or CurseForge upload took place.
CI now checks the prepared Maven publication, including its three jar classifiers, coordinates and checksums. A narrowly guarded recovery workflow resumes publication from the original successful release build, in the usual Maven → CurseForge → GitHub order.
Release stays unchanged
Version
0.4.0.114041, its tag atb9f06402602a677b249fbde7705973d9791e2db2, and all three release-jar checksums remain unchanged. The recovery cannot rebuild the jars or include gameplay, resource or documentation changes.Verification
Reproduced the original failure locally, then verified the repaired prepared-bundle path, rejection of an invalid bundle, publication task graph, full build/check/Javadoc/artifact/Eclipse checks and workflow syntax. The main and sources jars still match the immutable release bundle; the local Javadoc hash is also unchanged.