-
Notifications
You must be signed in to change notification settings - Fork 186
Gson upgrade to 2.13.2 2.29.x #6947
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
…leDateFormat for years below 2020 by replacing it with java.time.format.DateTimeFormatter and initialize test data in a test setup method to make sure that there's no CPU ticks between dates initializations.
|
@alexabird could you please review this PR? |
| date = getDate(); | ||
| propertyIsEqualToWithDate = getPropertyIsEqualToWithDate(getDate()); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❓ Why is getDate() called twice here? Should the date result from the first call just be passed into the getPropertyIsEqualToWithDate method?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed.
|
The target branch is codice:master - should it be updated to 2.29.x? |
What does this PR do?
This PR resolves CVEs with the current GSon version by upgrading to GSon 2.13.2
NOTE:
It has a dependency on country code changes in the following PR: codice/countrycode#37
Select relevant component teams:
Ask 2 committers to review/merge the PR and tag them here.
How should this be tested?
Any background context you want to provide?
What are the relevant tickets?
Fixes: https://jira.irad-launchpad.com/browse/ISR-22364
Notes on Review Process
Please see Notes on Review Process for further guidance on requirements for merging and abbreviated reviews.
Review Comment Legend: