[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
nuxt-gtag	4.1.0 → 5.0.0

---

Release Notes

johannschopplich/nuxt-gtag (nuxt-gtag)

v5.0.0

Compare Source

Migration

Nuxt 4 is required. The module no longer supports Nuxt 3. Nothing else in your configuration changes on that account.

A tag ID named twice is configured once. If the same ID appeared in both the id option and the tags array, both entries used to reach the config command, and the second overwrote the first. Only one survives now, and it is the id entry, which carries the top-level initCommands and config. Move any settings you kept in the duplicate tags entry up to the top level, or drop the id option and keep the entry in tags.

An existing dataLayer no longer stops initialization. initialize() used to do nothing at all when window.dataLayer was already present, which a third-party snippet such as Google Tag Manager creates before Nuxt hydrates. The module tracks the IDs it configured itself instead, so it now configures its tags alongside such a snippet rather than silently standing down. If you relied on the old behavior to let GTM own the page, stop calling initialize() – or set enabled to false.

---

   🚨 Breaking Changes

• Require Nuxt 4  -  by @​johannschopplich (f9d2e)

   🐞 Bug Fixes

• Accept a mixed array of tag IDs and tag objects  -  by @​johannschopplich (38562)
• Configure a tag ID that initialize receives at runtime  -  by @​johannschopplich (23694)
• Configure each tag ID exactly once  -  by @​johannschopplich (92aab)
• Track configured tag IDs instead of inferring them from dataLayer  -  by @​johannschopplich (c3bd0)

    View changes on GitHub

---

Configuration

📅 Schedule: (in timezone Asia/Taipei)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: 8971ea1b-2e71-4cc5-97b7-8e2edf19b514

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• Trigger review

• 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

[rileychh-dokploy-coscup]

Dokploy Preview Deployment

Name	Status	Preview	Updated (UTC)
Nuxt	❌ Failed	Preview URL	2026-11-11T17:58:37.187Z

[chatgpt-codex-connector]

Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-11-11T17:57:41.190622Z	2c79d92	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.