Skip to content

fix: simplify dependabot to only track SDK dependencies#1226

Merged
abueide merged 1 commit intomasterfrom
fix/dependabot-config
Apr 13, 2026
Merged

fix: simplify dependabot to only track SDK dependencies#1226
abueide merged 1 commit intomasterfrom
fix/dependabot-config

Conversation

@abueide
Copy link
Copy Markdown
Contributor

@abueide abueide commented Apr 13, 2026

Summary

Simplify dependabot configuration to only track SDK dependencies in the root workspace.

Problem

Currently tracking 10+ directories causing too many PRs per week:

  • Root workspace
  • 3 example/E2E apps (npm + ruby each)
  • E2E CLI

Example/E2E apps exist to test specific RN versions and shouldn't auto-update weekly.

Changes

  • Remove all example/E2E app directories from dependabot.yml
  • Keep only root workspace (actual SDK)
  • Dependencies will be grouped: production-dependencies + development-dependencies

Result

Before: 10+ individual PRs/week
After: 2 grouped PRs/week

Follow-up Actions

After merging this:

  1. Close existing example/E2E dependabot PRs (or they'll auto-close)
  2. Recreate PR chore(deps): bump the production-dependencies group across 1 directory with 47 updates #1222 (production-dependencies) to use new config

🤖 Generated with Claude Code

Remove example/E2E apps from dependabot automation:
- Example apps exist to test specific RN versions and shouldn't auto-update
- Dependencies are updated manually when upgrading test environments
- Only track root workspace (the actual SDK) for automated updates

Result: 2 grouped PRs/week instead of 10+ individual PRs
- production-dependencies group
- development-dependencies group

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
@abueide abueide merged commit 8e92f4b into master Apr 13, 2026
7 checks passed
@abueide abueide deleted the fix/dependabot-config branch April 13, 2026 19:47
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