Skip to content

Do not ignore introduced version when considering db specific field - #2425

Merged
keshav-space merged 1 commit into
mainfrom
fix-github-osv-db-specific
Sep 3, 2026
Merged

Do not ignore introduced version when considering db specific field#2425
keshav-space merged 1 commit into
mainfrom
fix-github-osv-db-specific

Conversation

@keshav-space

@keshav-space keshav-space commented Aug 27, 2026

Copy link
Copy Markdown
Member

resolves: #2323

Signed-off-by: Keshav Priyadarshi <git@keshav.space>
@keshav-space
keshav-space force-pushed the fix-github-osv-db-specific branch from 1958321 to fc584de Compare September 3, 2026 09:17
@keshav-space keshav-space changed the title fix: do not ignore introduced version when considering db specific field Do not ignore introduced version when considering db specific field Sep 3, 2026
@keshav-space
keshav-space merged commit c3adaf0 into main Sep 3, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

OSV parser ignores introduced version when considering database_specific field

1 participant