chore(deps): coordinated bump @tiptap/* 3.26.0 -> 3.26.1#226
chore(deps): coordinated bump @tiptap/* 3.26.0 -> 3.26.1#226JohnRDOrazio wants to merge 1 commit into
Conversation
Supersedes Dependabot PRs #211 (@tiptap/starter-kit) and #213 (@tiptap/pm) which couldn't merge individually — tiptap's internal peer-dep structure forces lockstep version bumps and each per-package PR failed `npm install` with ERESOLVE on @tiptap/core peer conflict. Bumping all 4 packages together (extension-link, pm, react, starter-kit) lets npm dedupe @tiptap/core@3.26.1 across the tree. Process note: regenerated package-lock.json from scratch (rm -rf node_modules package-lock.json && npm install) — npm's incremental resolver kept reporting stale "Found: extension-link@3.26.0" even after editing package.json, and only a full re-resolve produced a clean lockfile. PR #219's `groups: tiptap` config (just merged) means future minor/patch tiptap bumps come as one bundled PR, so this manual coordination shouldn't be needed again. Verification: npm ls @tiptap/extension-link @tiptap/pm @tiptap/react \ @tiptap/starter-kit @tiptap/core → all 5 at 3.26.1, @tiptap/core deduped across the tree npx tsc --noEmit → clean npm run lint → clean npm test -- --run → vitest 146/146 After this lands, #211 and #213 can be closed manually (they're now obsolete). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 19 minutes and 1 second. 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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
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.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
2 participants
Summary
Bumps all four
@tiptap/*direct dependencies from3.26.0to3.26.1in a single coordinated PR — supersedes Dependabot's per-package PRs #211 (starter-kit) and #213 (pm) which couldn't merge individually because tiptap's internal peer-dep structure forces lockstep version bumps.Why a manual coordinated PR
Per-package PRs fail
npm installwithERESOLVE:because each individual bump pulls in
@tiptap/core@3.26.1transitively while the unbumped sibling packages still require@tiptap/core@3.26.0exact. Together they dedupe cleanly.The merged PR #219 added a
groups: tiptapblock to.github/dependabot.ymlso future tiptap minors/patches arrive bundled — this manual coordination won't be needed again.Process note
npm install --save @tiptap/extension-link@3.26.1 @tiptap/pm@3.26.1 @tiptap/react@3.26.1 @tiptap/starter-kit@3.26.1failed with the same ERESOLVE because npm's incremental resolver kept reading staleextension-link@3.26.0state. The clean path that worked:package.jsonto^3.26.1on all four packagesrm -rf node_modules package-lock.json && npm installThe huge lockfile diff (1248 insertions, 984 deletions) is the expected reorganization of a fresh regenerate — the semantic delta is just the tiptap version bumps + their transitive
@tiptap/core@3.26.1deduplication.Verification
npm ls @tiptap/extension-link @tiptap/pm @tiptap/react @tiptap/starter-kit @tiptap/core→ all 5 at3.26.1,@tiptap/corededupednpx tsc --noEmit→ cleannpm run lint→ cleannpm test -- --run→ vitest 146/146 passingAfter merge
Close #211 and #213 manually — they're now obsolete (Dependabot's auto-close-on-supersede behavior is inconsistent for grouped configs introduced after the standalone PRs were opened).
🤖 Generated with Claude Code