Repository navigation
feat(ci): use minimal check GHA workflow - #400
Conversation
📝 WalkthroughWalkthroughThe ChangesMinimal check CI
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
.github/workflows/ci.yml (1)
23-25: 🔒 Security & Privacy | 🔵 Trivial | ⚡ Quick winPin the new third-party action to a full commit SHA.
@v1is a movable tag, so the action implementation can change without a workflow diff. Pin the verified release commit while retainingv1in a comment for maintainability. GitHub recommends full-length SHA pinning for third-party actions. (docs.github.com)🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/ci.yml around lines 23 - 25, Update the gominimal/check action reference to use the verified full commit SHA instead of the movable `@v1` tag, and retain `@v1` in an adjacent comment for maintainability. Keep the existing channel: unstable configuration unchanged.Source: MCP tools
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/workflows/ci.yml:
- Around line 23-25: Update the gominimal/check action reference to use the
verified full commit SHA instead of the movable `@v1` tag, and retain `@v1` in an
adjacent comment for maintainability. Keep the existing channel: unstable
configuration unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 48a88fe4-03c0-429d-bff6-a03540b14aae
📒 Files selected for processing (1)
.github/workflows/ci.yml
gominimal#311) The virtio microVM guest kernel was ~50 LTS patch releases behind. We deliberately do NOT per-CVE-track the kernel -- it's CVE-dark by design, since linux:linux_kernel would flood the digest with ~1,430 mostly-inapplicable driver/subsystem CVEs a virtio guest never compiles (see gominimal#400). Riding the latest 6.12 LTS backport stream IS the kernel's security posture, so bump it. - virtio-linux 6.12.43 -> 6.12.94. Tarball staged at gs://minimal-staging-archives/linux-6.12.94.tar.xz; sha256 e998a232... verified against kernel.org's signed sha256sums.asc. - virtio-kernel-raw tracks virtio-linux's version (it only decompresses that kernel), bumped in lockstep. - virtio-linux-detonation (6.18.36, a separate mainline detonation kernel) left unchanged. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Just uses the new GHA we made rather than shelling out ourselves.
Summary by CodeRabbit