Fix: Use correct oldest result date in vulns #3930
Merged
Conversation
This file contains 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
When parsing the result dates for vulnerabilities, the correct field is now used for the oldest result. When date parsing was added to the Vulnerability model class, the newest date was used accidentally.
Conventional Commits Report
🚀 Conventional commits found. |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #3930 +/- ##
=======================================
Coverage 60.04% 60.04%
=======================================
Files 1025 1025
Lines 25201 25201
Branches 7468 7468
=======================================
Hits 15133 15133
Misses 9124 9124
Partials 944 944 ☔ View full report in Codecov by Sentry. |
bjoernricks
approved these changes
Dec 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
When parsing the result dates for vulnerabilities, the correct field is now used for the oldest result.
Why
When date parsing was added to the Vulnerability model class, the newest date was used accidentally.
References
GEA-414
Checklist