Repository navigation
fix: pin spring to explicit version to avoid unstable milestone releases - #404
Merged
meotch merged 1 commit intoOct 5, 2026
Conversation
meotch
requested review from
SandhyaBhatia,
gerfboy,
mattnichols,
stevecl5 and
tessstoddard
as code owners
October 5, 2026 19:33
stevecl5
approved these changes
Oct 5, 2026
meotch
deleted the
mitch/pin_spring_to_explicit_version_to_avoid_milestone_releases
branch
October 5, 2026 21:42
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
3 participants
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 of Changes
Pins Spring to 4.1.1 to avoid pulling in unstable milestone releases
Fixes MC-16512
Public API Additions/Changes
None
Downstream Consumer Impact
None
How Has This Been Tested?
Tested locally against path-connector-central-pacific
Checklist: