-
Notifications
You must be signed in to change notification settings - Fork 9
feat(ci): harden #90
feat(ci): harden #90
Conversation
WalkthroughThis update introduces a new Dependabot configuration and modifies several GitHub Actions workflows. The workflows now reference specific commit SHAs for third-party actions instead of version tags, and some steps have updated parameters for security and clarity. No changes are made to the core application logic or exports. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 3
🧹 Nitpick comments (2)
.github/dependabot.yml (1)
1-6: Consider tightening update cadence and adding security-focused labelsMonthly checks are fine for low-risk projects, but GitHub-Action CVEs often need faster turnaround. A weekly (or even daily) schedule plus a
labels:section (e.g.security,dependencies) improves visibility and triage speed..github/workflows/publish.yml (1)
36-39: Ensure the auth token never leaks to logsWriting the token via
echois okay because GitHub redacts secrets, but adding the--no-echostyle heredoc removes even TRACE-level exposure:- - run: echo "//registry.npmjs.org/:_authToken=$NODE_AUTH_TOKEN" > ~/.npmrc + - run: | + cat <<EOF > ~/.npmrc +//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} +EOF
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
.github/dependabot.yml(1 hunks).github/workflows/build.yml(1 hunks).github/workflows/cla.yml(1 hunks).github/workflows/publish.yml(2 hunks).github/workflows/test.yml(1 hunks)
🔇 Additional comments (7)
.github/workflows/build.yml (2)
21-23: Good call pinningactions/checkoutand disabling credential persistence
Immutable SHAs +persist-credentials: falsemitigate supply-chain attacks and token bleed.
31-37: Cache action correctly pinned – LGTM
Pinningactions/cacheto a SHA is consistent with the hardening goal..github/workflows/test.yml (2)
8-10: Checkout step hardened correctly
Same rationale as the build workflow—looks good.
18-24: Cache action SHA pin approved
Consistent with security strategy..github/workflows/publish.yml (2)
12-14: Checkout pin + no credentials: good
Reduces risk of token exfiltration during releases.
24-31: Cache action correctly pinned
No issues spotted..github/workflows/cla.yml (1)
15-15: CLA Assistant pinned – solid
Locking the action to a commit aligns with the repo’s hardening goals.
|
Deprecated repo. Moved to https://github.com/cowprotocol/cow-sdk/tree/main/packages/app-data |
This PR hardens the CI by explicitly pinning all GitHub actions to their exact commit SHAs.
Summary by CodeRabbit