Merge Patchlevel categories of ODG findings #483
+3
−14
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
heldkat
changed the title
ccwienk
reviewed
Jun 26, 2025
There was a problem hiding this comment.
generally: lgtm
however, I wonder whether we will need to migrate existing data
/cc @zkdev | @8R0WNI3 | @TuanAnh17N
8R0WNI3
reviewed
Jun 27, 2025
Yes, in case we decide to replace existing categorisations, we have to adjust existing DB-entries with those old categorisations to use the new one instead. |
Co-authored-by: Tuan Anh Nguyen (TuanAnh17N) <tuan-anh_nguyen@gmx.de>
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 this PR does / why we need it:
Due to recent updates to the processing times of outdated OS, a differentiation between the
more-than-one-patchlevel-behindandone-patchlevel-behindcategories became obsolete. Here, we made the necessary adaptations to merge these two groups.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: