-
Notifications
You must be signed in to change notification settings - Fork 9
ci: [SEC-7263] Update dependency-scan workflow to use common-actions #1775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Replace launchdarkly/gh-actions with launchdarkly/common-actions for SEC-7263. Update to use runs-on runner pattern and add proper artifacts configuration. Co-Authored-By: Patrick Kaeding <[email protected]>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
|
Size Change: 0 B Total Size: 530 kB ℹ️ View Unchanged
|
Add id-token: write and contents: read permissions to both generate-nodejs-sbom and evaluate-policy jobs to enable access to private launchdarkly/common-actions repository. Co-Authored-By: Patrick Kaeding <[email protected]>
Add CUSTOM_GITHUB_TOKEN retrieval via release-secrets action to both jobs to enable access to private launchdarkly/common-actions repository. Co-Authored-By: Patrick Kaeding <[email protected]>
Switch from private common-actions to public gh-actions for SEC-7263. Simplify workflow structure to match working implementation. Co-Authored-By: Patrick Kaeding <[email protected]>
Remove custom runs-on configuration that was causing runner resolution failures. Simplify to standard ubuntu-latest for SEC-7263. Co-Authored-By: Patrick Kaeding <[email protected]>
Summary
Updates the dependency-scan GitHub Actions workflow to use the newer
launchdarkly/common-actions
format instead of the legacylaunchdarkly/gh-actions
format as part of security initiative SEC-7263.Key changes:
launchdarkly/gh-actions
tolaunchdarkly/common-actions
Testing approaches
The workflow changes should be validated by:
Review checklist
bom-*
pattern matches what the generate-sbom action producesLink to Devin run: https://app.devin.ai/sessions/434bb14b7bac4d81b9979b88965be92b
Requested by: Patrick Kaeding (@pkaeding)
Related Jira issue: SEC-7263: Investigate impact of compromised NPM packages: debug and chalk