Repository navigation
Fix gitlab schema for glsca report(AST-180720) - #1581
Merged
Merged
Conversation
cx-goncalo-lemos
previously approved these changes
Sep 29, 2026
cx-goncalo-lemos
previously approved these changes
Sep 30, 2026
# Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
cx-rakesh-kadu
approved these changes
Oct 12, 2026
cx-goncalo-lemos
approved these changes
Oct 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fixes GitLab schema validation failures (missing required keys: identifiers) on GL-SCA (dependency-scanning) reports. When a CVE has no advisory/reference data yet (e.g. very recently disclosed CVEs), collectScaPackageData() returned an empty identifiers slice, and the omitempty tag on GlScaDepVulnerabilities.Identifiers caused the JSON key to be dropped entirely which violates GitLab's schema requirement of at least one identifier per vulnerability (minItems: 1). GitLab then silently discards those findings from the Security Dashboard / Vulnerability Report.