[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
nuxt-gtag	^3.0.1 → ^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

v4.1.0

Compare Source

   🚀 Features

• Add multi-tenancy support with consent mode and dynamic tag IDs  -  by @​johannschopplich (e5d5f)

    View changes on GitHub

v4.0.0

Compare Source

   🚨 Breaking Changes

• Upgrade to Nuxt v4  -  by @​johannschopplich in #​102 (291f8)

    View changes on GitHub

v3.0.3

Compare Source

   🐞 Bug Fixes

• Remove runtime config override  -  by @​johannschopplich in #​98 (99f72)

    View changes on GitHub

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• 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.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.