Repository navigation
Remove cached CustomCrops libraries and stale archive - #16
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.
Summary
Remove 29 cached CustomCrops dependency JARs and the old CustomCrops ZIP (about 23.7 MiB). The ZIP retained fertility settings removed from the current YAML. Keep authored crop and ItemsAdder assets, ignore regenerated libraries/archives, and document creating a configuration ZIP from the deployment commit.
Documentation impact
Contract
clean verifybuild passed. All 167 unit tests passed. Removed paths match narrow ignore rules; current authored configuration is unchanged. Documentation manifest, links and impact checks passed.