ci: dependency-scan release gate (CRA Annex I Part I(1))#310
Merged
Conversation
Expose dependency-scan as a reusable workflow (workflow_call) and gate publish-studio-all on it, so a known-vulnerable dependency blocks the release and the platform publish pipelines that cascade from it. Also drop the stale internal compliance/cra/ path reference from the scan comment. SAST (CodeQL) and secret scanning are provided organisation-wide via GitHub Advanced Security default setup, so no repo-level CodeQL workflow is needed.
hendrikmennen
force-pushed
the
cra/codeql-and-release-gate
branch
from
040349b to
f55c327
Compare
hendrikmennen
changed the title
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
1 participant
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.
Makes the vulnerable-dependency scan a required release gate for OneWare Studio, closing the remaining EU CRA (Regulation (EU) 2024/2847) Annex I Part I(1) technical gap.
Changes
dependency-scan.ymlnow also exposesworkflow_call.publish-studio-all.ymlruns it as ascanjob and thereleasejobneeds: scan. A known-vulnerable NuGet dependency now blocks the GitHub Release, and since every platform publish requiresworkflow_run.conclusion == 'success', the entire publish cascade is blocked too.compliance/cra/path reference from the scan comment.Note on SAST
CodeQL and secret scanning are enabled organisation-wide via GitHub Advanced Security default setup, so no repo-level CodeQL workflow is added here.
CRA mapping
No product code changes; CI only.