Repository navigation
build: resolve shared plugin APIs from verified releases - #6
Merged
Merged
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
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.
Shared plugin APIs previously depended on copied private JARs and local system paths. Build and release jobs now resolve declared plugin APIs from checksum-verified GitHub releases, install their native Maven coordinates with provided scope, and record exact dependency versions and checksums with each build.
Local POM versions remain explicit for pinned rebuilds. CI selects published releases; Cooking and InteractibleFurniture retain their existing preview channels. AdvancedCrafting now uses the new public source-built 1.2.2 release, with its previous private 1.2.1 retained for explicitly pinned rollback. MusicalInstruments 2.5 remains private until compatible source is available. Minimal provider POMs and exclusions prevent recursive resolution of existing source dependency cycles.
Validation: 18 shared installer tests passed; workflow syntax and dependency configuration checked; all 26 migrated repositories passed local Maven clean verify. This PR runs full Maven verification with the selected releases. No runtime deployment is performed. Reverting this commit restores the former preparation path; existing private artifacts are retained.