Skip to content

chore(deps): group @tiptap/* updates so peer-dep-coupled bumps land together#219

Merged
JohnRDOrazio merged 1 commit into
mainfrom
chore/dependabot-group-tiptap
Jun 16, 2026
Merged

chore(deps): group @tiptap/* updates so peer-dep-coupled bumps land together#219
JohnRDOrazio merged 1 commit into
mainfrom
chore/dependabot-group-tiptap

Conversation

@JohnRDOrazio

Copy link
Copy Markdown
Member

Summary

Adds a groups: block to the npm update config in .github/dependabot.yml matching @tiptap/*, so future tiptap minor/patch bumps arrive as a single bundled PR instead of one-per-package.

Why

PRs #211 (@tiptap/starter-kit 3.26.0 → 3.26.1) and #213 (@tiptap/pm 3.26.0 → 3.26.1) sat open with failing CI because tiptap's internal peer-dep structure forces lockstep version bumps. The actual npm install error:

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error While resolving: @tiptap/react@3.26.0
npm error Found: @tiptap/core@3.26.1
npm error peer @tiptap/core@"3.26.1" from @tiptap/extension-blockquote@3.26.1
npm error   @tiptap/extension-blockquote@"^3.26.0" from @tiptap/starter-kit@3.26.0
npm error     @tiptap/starter-kit@"^3.26.0" from the root project
npm error Could not resolve dependency:
npm error peer @tiptap/core@"3.26.0" from @tiptap/react@3.26.0

@tiptap/pm@3.26.1 and @tiptap/starter-kit@3.26.1 individually pull in @tiptap/core@3.26.1, but @tiptap/react@3.26.0 (in the root project) has a peer requirement on @tiptap/core@3.26.0 exact. Bumped together they install cleanly. Dependabot's default single-PR-per-package shape makes this fail every minor.

What changes

- package-ecosystem: "npm"
  directory: "/"
  schedule:
    interval: "weekly"
+ groups:
+   tiptap:
+     patterns:
+       - "@tiptap/*"

Next weekly Dependabot run will detect the new group config and produce a single bundled PR for any tiptap updates pending.

Doesn't fix

Why only @tiptap/* (not also @types/*, eslint*, etc.)

Keeping the change minimal to the concrete failure that motivated it. Other co-coupled families can be added in follow-ups as they bite — premature grouping risks bundling unrelated updates and making rollback harder.

Test plan

🤖 Generated with Claude Code

…ogether

PRs #211 and #213 sat open with failing CI because Dependabot raises
one PR per package and tiptap's internal peer-dep structure forces
lockstep version bumps:

  npm ERESOLVE could not resolve
    While resolving: @tiptap/react@3.26.0
    Found: @tiptap/core@3.26.1
    peer @tiptap/core@"3.26.0" from @tiptap/react@3.26.0

@tiptap/pm@3.26.1 and @tiptap/starter-kit@3.26.1 individually pull in
@tiptap/core@3.26.1, which conflicts with @tiptap/react@3.26.0's peer
requirement on core@3.26.0 exact. Bumped together they install cleanly.

Adds a `tiptap` group matching `@tiptap/*` so future minor/patch bumps
arrive as a single bundled PR that npm install accepts the first time.

Doesn't fix the current open #211/#213 (their existing PRs need closing
or Dependabot will recreate the group on next weekly run, leaving the
old ones to be closed manually).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jun 16, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@JohnRDOrazio, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 26 minutes and 11 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 00063be1-a955-49b3-8ec0-0e4a60cb68aa

📥 Commits

Reviewing files that changed from the base of the PR and between d880c8f and b8989af.

📒 Files selected for processing (1)
  • .github/dependabot.yml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/dependabot-group-tiptap

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@JohnRDOrazio JohnRDOrazio merged commit 3ff77e8 into main Jun 16, 2026
10 checks passed
@JohnRDOrazio JohnRDOrazio deleted the chore/dependabot-group-tiptap branch June 16, 2026 15:13
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