Modernize docs CI and dependency maintenance - #20
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
nextcommerce-docs | 9ac933c | Commit Preview URL Branch Preview URL |
Jul 31 2026, 08:57 AM |
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/checkout@v4 | ||
| - uses: actions/checkout@v6 |
There was a problem hiding this comment.
WARNING: actions/checkout@v6 is pinned to a mutable major-version tag. A compromised tag retag would silently swap the action implementation on every CI run. Pin to the full commit SHA (e.g. actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11) and reference # v6.0.0 in a comment for upgrades.
This applies to actions/checkout@v6 (lines 13, 27) and actions/setup-node@v6 (lines 15, 29).
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
|
|
||
| - run: npm run build | ||
|
|
||
| security-audit: |
There was a problem hiding this comment.
WARNING: The new security-audit job skips npm ci/npm install and runs npm audit --omit=dev directly on a fresh checkout. While npm audit reads package-lock.json without node_modules, this diverges from how the build job resolves dependencies and can mask vulnerabilities whose fix relies on npm install resolution (e.g. overrides, peer-dep-driven resolutions) being materialized. Consider running npm ci before npm audit so both jobs share the same resolved tree.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| interval: weekly | ||
| open-pull-requests-limit: 5 | ||
|
|
||
| - package-ecosystem: github-actions |
There was a problem hiding this comment.
SUGGESTION: Add a groups block (and consider labels) so weekly Dependabot runs batch related Action updates into a single PR. As written, every action version bump on its own dependency will open a separate PR up to open-pull-requests-limit: 5, which can quickly exhaust the limit and stall security updates. Example:
groups:
actions:
patterns:
- "*"Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "overrides": { | ||
| "postcss": "8.5.10" | ||
| "postcss": "8.5.25", | ||
| "sharp": "0.35.3" |
There was a problem hiding this comment.
WARNING: The new sharp override pins a transitive of next (optionalDependencies: "sharp": "^0.34.5") to 0.35.3 — a major-version jump. Sharp 0.35 introduced changes to libvips packaging (new @img/sharp-wasm32/@img/sharp-webcontainers-wasm32 variants, broader libc classification) and may include image-processing API or default-behavior changes that affect Next.js image optimization output. Recommend: (1) diff Next.js's usage of sharp's public API against 0.35's changelog, (2) re-run the production build and visually verify a representative image pipeline (next/image with optimization) before merging, and (3) consider pinning to the latest 0.34.x patch instead if the only goal is the advisory fix.
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
Code Review SummaryStatus: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (4 files)
Fix these issues in Kilo Cloud Previous Review Summary (commit 5a779ee)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 5a779ee)Status: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)WARNING
SUGGESTION
Files Reviewed (4 files)
Reviewed by minimax-m3 · Input: 22.8K · Output: 931 · Cached: 56.3K |
Summary
actions/checkoutandactions/setup-nodeto v6Why
A newly published dependency advisory caused
npm auditto stop the CI job before the documentation build ran. The workflow also used v4 Actions running on the deprecated Node 20 action runtime.Validation
npm cinpm audit --omit=dev— 0 vulnerabilitiesnpm run build— link checks pass and 268 static pages buildactionlint .github/workflows/ci.yml