Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
version: 2

updates:
- package-ecosystem: npm
directory: /
schedule:
interval: weekly
open-pull-requests-limit: 5

- package-ecosystem: github-actions

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

directory: /
schedule:
interval: weekly
open-pull-requests-limit: 5
groups:
actions:
patterns:
- "*"
20 changes: 16 additions & 4 deletions .github/workflows/ci.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,15 +10,27 @@ jobs:
build:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0

- uses: actions/setup-node@v4
- uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
with:
node-version: '22'
cache: npm

- run: npm ci

- run: npm audit --omit=dev

- run: npm run build

security-audit:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

runs-on: ubuntu-latest
steps:
- uses: actions/checkout@d23441a48e516b6c34aea4fa41551a30e30af803 # v6.1.0

- uses: actions/setup-node@249970729cb0ef3589644e2896645e5dc5ba9c38 # v6.5.0
with:
node-version: '22'
cache: npm

- run: npm ci

- run: npm audit --omit=dev
1 change: 1 addition & 0 deletions next.config.mjs
Original file line number Diff line number Diff line change
Expand Up @@ -10,6 +10,7 @@ const config = {
outputFileTracingRoot: repoRoot,
reactStrictMode: true,
images: {
// Static exports do not use Next.js's Sharp-based image optimizer.
unoptimized: true,
},
};
Expand Down
Loading