Update Spring Boot to 2.5.3 to address multiple high & critical security issues #37
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.
This PR addresses ~60 issues that privy was flagging in the build process. Addressing those issues required updating Spring Framework from the 1.5.10 version we were using up to 2.5.3. That required a code change - findOne became findById and needed an "OrElseThrow()" method call. I also had to add an explicit dependency since the javax.validators.* are no longer implicitly included in the Spring web starter. This PR should probably be squashed and merged.