Changed Renovate grouping to bump @tryghost/limit-service on its own#27916
Conversation
- limit-service bumps are feature-tied: each new flag in `lib/config.js` is paired with BREAD/limit-helper code in this repo, so the version bump needs to land as its own reviewable PR - riding in with unrelated admin-support package updates (`color-utils`, `members-csv`, etc.) made the dependency PR harder to reason about and harder to coordinate with the consuming change Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis pull request modifies the Renovate dependency management configuration to separate 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Splits
@tryghost/limit-serviceout of the "TryGhost admin support packages" Renovate group so its version bumps come out as their own PR.Why
Unlike the other packages in that group (
color-utils,custom-fonts,members-csv,timezone-data), limit-service bumps are feature-tied: each new entry in itslib/config.jsallowlist is paired with consuming BREAD-service / limit-helper code here in Ghost. We need the version bump to land as a reviewable, single-package PR so it can be coordinated with the consuming change (and so a flaky CI run on an unrelated admin-support bump doesn't block it).No other behaviour changes — limit-service still respects the rest of the existing config (schedule, automerge windows, dashboard approval for majors, etc.).
Test plan
Update dependency @tryghost/limit-servicePR rather than bundling it into the admin-support group.🤖 Generated with Claude Code