Skip to content

chore: enable dependabot for npm and cargo dependencies #138

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
szegedi merged 2 commits into from
Jun 22, 2026
Merged

chore: enable dependabot for npm and cargo dependencies #138

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
46eaa5a
chore: enable dependabot for npm and cargo dependencies
szegedi Jun 22, 2026
161ab74
chore: add lockfile and dependabot entry for test/crashtracker
szegedi Jun 22, 2026
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
53 changes: 53 additions & 0 deletions .github/dependabot.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,3 +15,56 @@ updates:
gh-actions-packages:
patterns:
- "*"

- package-ecosystem: "npm"
directory: "/"

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 22, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Add the crashtracker npm manifest

When test/crashtracker dependencies such as express or body-parser need a security or compatibility bump, this npm entry is scoped only to /, so Dependabot will watch the root package.json/yarn.lock but never open updates for test/crashtracker/package.json and its lockfile, even though scripts/test.sh installs that package for the crashtracker test. Add a second npm entry, or use directories including /test/crashtracker, so the test package is covered too.

Useful? React with 👍 / 👎.

@szegedi szegedi Jun 22, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

The comment is valid as test/crashtracker/package.json has real dependencies (express, body-parser, @datadog/segfaultify) that won't be watched by the root-only entry.

That said, test/crashtracker has no lockfile of its own (package-lock.json or yarn.lock), so Dependabot will not be able to reliably track it. It skips directories with no lockfiles. Also, @datadog/segfaultify would presumably be excluded the same way @datadog/* is excluded from GitHub Actions (though the npm entry doesn't have that exclusion currently).

The fix is presumably to commit a lockfile there?

@gyuheon0h gyuheon0h Jun 22, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Yep, I think your most recent commit 161ab74 should address this

schedule:
interval: "weekly"
versioning-strategy: "increase"
labels:
- dependabot
- dependencies
- javascript
- semver-patch
groups:
patch-updates:
update-types:
- "patch"
minor-updates:
update-types:
- "minor"

- package-ecosystem: "npm"
directory: "/test/crashtracker"
schedule:
interval: "weekly"
versioning-strategy: "increase"
labels:
- dependabot
- dependencies
- javascript
- semver-patch
groups:
patch-updates:
update-types:
- "patch"
minor-updates:
update-types:
- "minor"

- package-ecosystem: "cargo"
directory: "/"
schedule:
interval: "weekly"
labels:
- dependabot
- dependencies
- rust
- semver-patch
groups:
patch-updates:
update-types:
- "patch"
minor-updates:
update-types:
- "minor"
Loading
Loading