chore(dependabot): weekly + grouped updates to cut Chromatic snapshots#127
Merged
Conversation
Dependabot was the dominant Chromatic snapshot drain: ~65 of the last 100 Chromatic builds were Dependabot PRs, each a FULL ~89-story rebuild (a lockfile change defeats TurboSnap — a dependency could affect any component), amplified by daily cadence, ungrouped per-package PRs, and a fresh rebuild on every rebase of every open PR. That alone burned a month's OSS-tier budget (7,500) in ~5 days. Switch npm + github-actions updates to weekly, and group the dev-tooling churn into a single PR (plus the existing react/react-dom group; majors stay ungrouped). One grouped weekly PR ≈ one build instead of many. Chromatic still runs on Dependabot PRs — visual checks are NOT skipped, there are just far fewer of them. Auto-merge is preserved: the dev group is dev-only + non-major, matching the dependabot-auto-merge gate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Dependabot is the dominant Chromatic snapshot drain. Of the last 100 Chromatic builds (~5 days), 65 were Dependabot PRs, and each is a full ~89-story rebuild — a Dependabot bump always changes the lockfile, and a lockfile change defeats TurboSnap (Chromatic full-rebuilds because a dependency could affect any component). Daily cadence + one PR per package + a fresh full rebuild on every rebase of every open PR (e.g.
base-ui/reactrebuilt 5× in one night) burned a month's OSS-tier budget (7,500) in ~5 days.What
.github/dependabot.ymlonly:weekly(wasdaily).@types/*, …) into one PR via adev-dependenciesgroup (development + minor/patch). Majors stay ungrouped for individual review.react/react-domgroup (exact-version match, PR chore(deps-dev): bump react from 19.2.5 to 19.2.6 #72).One grouped weekly PR ≈ one Chromatic build instead of many.
What this does NOT change
skip:option was set aside to keep bot PRs visually checked).dependency-type == direct:development && update-type != majorgate independabot-auto-merge.yml.fetch-metadatareports grouped dev PRs asdirect:developmentwith the highest (non-major) bump.Expected effect
Cuts Dependabot-origin builds ~80–90% (frequency + grouping + no rebase amplification). Estimated overall Chromatic snapshots/month: ~45k → ~10–13k. A meaningful reduction, though each remaining bot build is still a full rebuild, so it may not fully clear the 7,500 tier on its own — the
skip:option remains available later if needed.Config-only (YAML) — no changeset (does not affect the published package).
🤖 Generated with Claude Code