Skip to content

chore: Group Dependabot updates and align commit prefixes.#235

Merged
goloroden merged 1 commit into
mainfrom
configure-dependabot-grouping
Jun 27, 2026
Merged

chore: Group Dependabot updates and align commit prefixes.#235
goloroden merged 1 commit into
mainfrom
configure-dependabot-grouping

Conversation

@goloroden

Copy link
Copy Markdown
Member

What

Overhaul the Dependabot configuration to group updates and make commit prefixes release-aware, consistent with the org-wide convention rolled out across the thenativeweb repositories.

Grouping

  • Minor and patch updates are bundled into one pull request per ecosystem.
  • Major updates keep coming in individually, so breaking changes stay isolated and reviewable.
  • Where an ecosystem distinguishes production from development dependencies (npm, pip, composer, mix), they are split into separate *-production / *-development groups.

Commit prefixes (release behavior)

Prefixes now reflect what actually ships in the product: ecosystems whose updates change the released artifact use fix (triggering a patch release via get-next-version), while CI (github-actions), test, and documentation tooling uses chore (release-neutral). Production dependencies use fix, development/test dependencies use chore.

Assignee

Replaces the team assignee thenativeweb/internal_dev (which GitHub rejects, since assignees must be individual users, not teams) with goloroden. Team review already runs through CODEOWNERS plus branch protection, so nothing is lost.

Why

Reduce the volume of routine dependency pull requests without hiding breaking changes, and align the release-triggering behavior of dependency updates with whether they actually affect the shipped product.

🤖 Generated with Claude Code

https://claude.ai/code/session_01BEb1kvMyuGfpybysH3N7Ln

Bundle minor and patch updates per ecosystem into one pull request each,
while major updates keep coming in individually so breaking changes stay
isolated and reviewable.

Align commit-message prefixes with what ships in the product: ecosystems
whose updates change the released artifact use `fix` (triggering a patch
release), while CI, test, and documentation tooling uses `chore`
(release-neutral). Where an ecosystem distinguishes production from
development dependencies, they are split into separate groups so the two
prefixes apply cleanly.

Replace the team assignee (which GitHub rejects, since assignees must be
individual users) with goloroden; team review already runs through
CODEOWNERS and branch protection.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BEb1kvMyuGfpybysH3N7Ln
@goloroden goloroden requested a review from a team as a code owner June 27, 2026 12:12
@goloroden goloroden self-assigned this Jun 27, 2026
@goloroden goloroden merged commit 75b0010 into main Jun 27, 2026
5 checks passed
@goloroden goloroden deleted the configure-dependabot-grouping branch June 27, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant