Repository navigation
fix(circleci): use open_source-managed context for security-scans - #153
Conversation
Standardizes the CircleCI context on the security-scans job (prodsec/security_scans) to open_source-managed, matching the convention used across the majority of snyk/engines_sca-scanners repos. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
This comment has been minimized.
This comment has been minimized.
PR Reviewer Guide 🔍
|
gergo-papp
left a comment
There was a problem hiding this comment.
Verified: single-file change to .circleci/config.yml, only the CircleCI context swap to open_source-managed. No other config changes and no leftover references to the old context. LGTM.
Summary
security-scansjob (wrappingprodsec/security_scans) in.circleci/config.ymlwas using theanalysis_unifyCircleCI context.open_source-managed, the context used by the large majority ofsnyk/engines_sca-scanners-owned repos for this job.Context
Identified as part of an audit of
prodsec/security_scans,prodsec/container_scan, andpublish/publishCircleCI contexts across all sca-scanners repos.Test plan
security-scansjob runs successfully on this branch/PR with the new contextSNYK_TOKENand other required env vars are present inopen_source-managed