🔒 security(release): ship v1.4.3 hardening pass - #138
Conversation
gate_status: skill
gate_status: skill
Exercise exact and wildcard image/plugin push rules across global and named-client policy, including the explicit acknowledgement path. gate_status: skill
Treat image and plugin pushes as local-artifact exfiltration surfaces even though the Docker API exposes them as writes, while retaining the existing opt-in key for compatibility. gate_status: skill
Parse the deployed Vercel policy contract and require the catch-all CSP, anti-framing, MIME, referrer, permissions, image-origin, and script-origin invariants. gate_status: skill
Apply a root catch-all Vercel policy for the marketing and copied docs exports, preserving static Next.js and same-origin analytics compatibility without enabling unsafe-eval or external script origins. gate_status: skill
Render the actual DaemonSet and require non-root identity, runtime-default seccomp, read-only filesystem, no escalation, dropped capabilities, and supplemental socket-group compatibility. gate_status: skill
Default the pod to Chainguard UID/GID 65532 with runAsNonRoot and RuntimeDefault seccomp while preserving the documented supplemental Docker-socket group override. gate_status: skill
Document the embedded ownership boundary, fresh authorization semantics, push exfiltration acknowledgement, Vercel policy, Helm hardening, migration impact, regression evidence, and scanner disposition in Sockguard’s established release-note voice. gate_status: exempt
gate_status: skill
gate_status: exempt
gate_status: skill
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Review limit reached
Next review available in: 4 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (21)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
mainVerification
lefthook run pre-push(GoReleaser snapshot, golangci-lint, race suite, govulncheck, fuzz smoke, dedupe, Knip, Biome, 89 tests, static builds, clean-tree)zizmor .github/workflows— no findings (10 ignored, 22 suppressed)helm lint chart/sockguardhelm template sockguard chart/sockguardv1.4.3CHANGELOG extractionRelease choreography
After merge and exact
v1.4.3tag verification, merge this stable line forward intodev/v1.5, preparev1.5.0-rc.2, and reset the v1.5 stable soak.