Add vulnerability scan gate to release workflows#1396
Merged
Conversation
Add a vulnerability-scan job to both release.yml and release-thin.yml that must pass before the publish job can run. The scan uses OWASP Dependency Check with -DfailBuildOnCVSS=7, which fails the build if any dependency has a CVSS score >= 7 (high/critical). The publish job has `needs: vulnerability-scan`, making the scan a hard gate — not just a notification. Scan reports are uploaded as artifacts for audit trail. Both jobs are currently disabled (if: false) per the publishing freeze. When releases are re-enabled, the scan gate is automatically active. Signed-off-by: Gopal Lal <gopal.lal@databricks.com> Co-authored-by: Isaac Signed-off-by: Gopal Lal <gopal.lal@databricks.com>
vikrantpuppala
approved these changes
Apr 9, 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
2 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.
Summary
Add a hard vulnerability scan gate to both release workflows (uber JAR and thin JAR). Currently the OWASP vulnerability scan runs weekly as a separate workflow — the release can proceed even if critical vulnerabilities are found.
Changes
vulnerability-scan(gate) andpublish(needs scan to pass)vulnerability-scangate +publish-thin(needs scan)-DfailBuildOnCVSS=7— fails the build on any CVSS >= 7 (high/critical) findingif: false) per publishing freeze — scan gate activates automatically when releases are re-enabledSecurity context
This addresses the supply chain security audit finding Q28: "Can artifacts with failed scans be used by consumers?" Previously YES — now NO.
NO_CHANGELOG=true
This pull request was AI-assisted by Isaac.