chore(nuxt-toc): update maintainer, docs URL, and metadata - #1622
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review. 📝 WalkthroughWalkthroughThe Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The metadata update is consistent with the repository contract and has no actionable merge risk. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (4 passed)
Full details: Linked Issues checkExplanation For Resolution Provide reviewable evidence for the ✨ 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 |
Updates
nuxt-toclisting metadata after taking over maintainership.thaikolja), including Bluesky handle from GitHub social accounts>=3.0.0(registry spelling for Nuxt 3 and 4;pnpm syncmerges this from publishedmodule.jsonacross majors)The published npm package still requires Nuxt
^3.16.0 || ^4.0.0viameta.compatibility/ peerDependencies. This YAML only feeds nuxt.com/modules.Replaces closed #1575. The previous fork-internal PR used an invalid range (
>=3.0.0 | >= 4.0.0); a single|is not valid semver, and>=3.0.0already includes Nuxt 4.