Conversation
…ekly-non-major-updates chore(deps): update github/codeql-action digest to 015d8c7 (feature/beta-release)
There was a problem hiding this comment.
Pull request overview
This PR updates the github/codeql-action/upload-sarif action in the security-pr workflow from an older commit SHA (b1b1e44da9bac3c3c733dd0dbecc16d3c7889499) to a newer one (015d8c7cbcbb8e7252a7dccfe81a90aa176260b2). The PR title "Nightly > Main CI Remediation" suggests this is part of broader CI/CD maintenance work to bring the main branch workflows up to date with changes made in the nightly branch.
Changes:
- Updated the CodeQL SARIF upload action to a newer commit SHA in the security-pr workflow
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
✅ Supply Chain Verification Results✅ PASSED 📦 SBOM Summary
🔍 Vulnerability Scan
📎 Artifacts
Generated by Supply Chain Verification workflow • View Details |
fix: enforce fresh nightly promotion quality gates Ensure promotion decisions are based on current nightly HEAD evidence instead of stale workflow history. Add native CodeQL branch triggers so security analysis runs on nightly/main promotion paths. Convert nightly and weekly automation to dispatch required checks only when missing for the exact HEAD commit, preventing duplicate/racing runs while guaranteeing check presence. Harden weekly health verification with retry polling so transient scheduling delays do not produce false negatives. This reduces false blocking and ensures nightly-to-main promotion uses current, deterministic CI state. Refs: #712
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
2 participants
No description provided.