Skip to content

chore(nuxt-toc): update maintainer, docs URL, and metadata - #1622

Merged
danielroe merged 3 commits into
nuxt:mainfrom
thaikolja:nuxt-toc-updated-metadata
Sep 19, 2026
Merged

danielroe merged 3 commits into
nuxt:mainfrom
thaikolja:nuxt-toc-updated-metadata

Conversation

@thaikolja

Copy link
Copy Markdown
Contributor

Updates nuxt-toc listing metadata after taking over maintainership.

  • Website: documentation
  • Maintainer: Kolja Nolte (thaikolja), including Bluesky handle from GitHub social accounts
  • Compatibility: >=3.0.0 (registry spelling for Nuxt 3 and 4; pnpm sync merges this from published module.json across majors)

The published npm package still requires Nuxt ^3.16.0 || ^4.0.0 via meta.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.0 already includes Nuxt 4.

@coderabbitai

coderabbitai Bot commented Sep 18, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: ff6469d1-3280-4648-b891-e6e28ff0034a

📥 Commits

Reviewing files that changed from the base of the PR and between c541abd and 72afae5.

📒 Files selected for processing (1)
  • modules/nuxt-toc.yml
🚧 Files skipped from review as they are similar to previous changes (1)
  • modules/nuxt-toc.yml

Included review availability: Your plan provides up to 4 included reviews per hour; 2 remain after this review.


📝 Walkthrough

Walkthrough

The nuxt-toc module entry now links to its GitHub Pages website. It replaces the maintainer hanyujie2002 with Kolja Nolte, updates the GitHub handle to thaikolja, and adds the Bluesky handle thaikolja.bsky.social. Other module metadata remains unchanged.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~3 minutes

Merge Risk: ⚪ Minimal · up to 72afa

The metadata update is consistent with the repository contract and has no actionable merge risk.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Linked Issues check ❓ Inconclusive For #1575, the diff updates the nuxt-toc registry entry with the project documentation URL, Kolja Nolte/thaikolja ownership, the Bluesky handle, and Nuxt compatibility >=3.0.0. These changes s… Provide reviewable evidence for the nuxt-toc package version, @nuxt/content v2 and v3 compatibility, Nuxt 3 and Nuxt 4 validation, and successful linting. The available repository evidence is insufficient to decide those #1575 requireme…
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the metadata changes, including the maintainer and documentation URL updates.
Description check ✅ Passed The description directly explains the metadata updates, compatibility range, maintainership transition, and relationship to the previous pull request.
Out of Scope Changes check ✅ Passed All four changed metadata fields are connected to #1575 or to the module listing required to represent that release: documentation URLs, maintainer ownership, maintainer social identity, and Nuxt comp…
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Full details: Linked Issues check

Explanation

For #1575, the diff updates the nuxt-toc registry entry with the project documentation URL, Kolja Nolte/thaikolja ownership, the Bluesky handle, and Nuxt compatibility >=3.0.0. These changes support the ownership and documentation objectives. The reviewed repository contains no evidence that the published package is version 3.0.0, supports @nuxt/content v2 and v3, or was validated with the required Nuxt versions and lint checks. The registry metadata cannot establish those requirements.

Resolution

Provide reviewable evidence for the nuxt-toc package version, @nuxt/content v2 and v3 compatibility, Nuxt 3 and Nuxt 4 validation, and successful linting. The available repository evidence is insufficient to decide those #1575 requirements.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create a new PR

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.

@danielroe
danielroe merged commit 312c581 into nuxt:main Sep 19, 2026
6 checks passed
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.

2 participants