[johannschopplich]

🔗 Linked issue

None.

📚 Description

Raises the compatibility.nuxt range of five modules to what their current releases require: nuxt-api-party to >=4.4.0, nuxt-prepare, nuxt-gtag and @nuxtjs/plausible to >=4.0.0, and nuxt-vitalizer to >=4.6.0.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

Five module compatibility declarations now set higher minimum Nuxt versions. The new minimums are Nuxt 4.4.0 for api-party, 4.0.0 for gtag, plausible, and prepare, and 4.6.0 for vitalizer.

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

Merge Risk: Minimal · previous review 5932c

This updates the declared minimum Nuxt versions for five modules and touches no runtime code. No concrete merge-blocking risk was found.

Pre-merge checks: 4

Check name	Status	Explanation
Title check		The title names the change: raising the Nuxt compatibility range of five named modules (api-party, gtag, plausible, prepare, vitalizer). The raw summary and objectives confirm that each module's compa…
Description check		The description follows the template's main section, Description, and states what changed and why: each module's compatibility.nuxt range is raised to match its current release. The Linked issue secti…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title names the change: raising the Nuxt compatibility range of five named modules (api-party, gtag, plausible, prepare, vitalizer). The raw summary and objectives confirm that each module's compatibility.nuxt range is the only change. The title is concise and specific, and it uses the conventional chore prefix.

Full details: Description check

Explanation

The description follows the template's main section, Description, and states what changed and why: each module's compatibility.nuxt range is raised to match its current release. The Linked issue section says None, which the template allows because an issue is optional. The template's AI-use and module-listing guidance is not addressed, but the description is short and accurate, and the change is a one-line-per-file version bump, so the description is mostly complete.

Finishing Touches

Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: a1bcf822-067f-46de-803b-5e700ca3d9e1

Commits

Reviewing files that changed from the base of the PR and between 52c7806 and 5932c1c.

Files selected for processing: 5

• modules/api-party.yml
• modules/gtag.yml
• modules/plausible.yml
• modules/prepare.yml
• modules/vitalizer.yml

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.