Repository navigation
Conversation
Dependabot security updates are not covered by version-update groups, so each vulnerable dependency opens its own PR. Add a group with applies-to: security-updates so they arrive as a single PR. Signed-off-by: Tiger Kaovilai <passawit.kaovilai@gmail.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kaovilai The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to
|
There was a problem hiding this comment.
🟢 Approval recommended
The minimal configuration correctly separates version and security update grouping, with no blocking issues identified.
No open issues 🎉
What changed in this PR
Adds Dependabot configuration for the root Go module, grouping security updates separately from routine version updates to reduce individual dependency PRs.
Changes:
- Schedules weekly Go module version updates in one group.
- Defines a separate group for all Go module security updates.
| File | Description |
|---|---|
.github/dependabot.yml |
Configures weekly Go updates and separate version and security update groups. |
Review effort: Balanced
Summary
Adds a minimal
.github/dependabot.ymlfor gomod with one group for version updates and one for security updates.Dependabot version-update groups do not apply to security updates, so each vulnerable dependency opens its own PR (e.g. several open at once). A group with
applies-to: security-updatescollapses them into one PR.Testing
Config-only change. Dependabot validates the file on merge and surfaces errors under Insights > Dependency graph > Dependabot.
Note
Responses generated with Claude (model: Claude Sonnet 5.5)
🤖 Generated with Claude Code
Summary by CodeRabbit