Skip to content

Release - #4

Merged
kisztof merged 1 commit into
mainfrom
changeset-release/main
Aug 28, 2026
Merged

Release#4
kisztof merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@stackmade/gtm-as-code@0.5.0

Minor Changes

  • 052149c: Extend protected resources to GA4. protected: true on a ga4.dimensions/metrics/keyEvents
    entry now needs --allow-destroy-protected before apply deletes it, tracked in
    .analytics/state.json since GA4 has no field of its own to stamp the flag into (GTM resources
    already worked this way).

  • 694b6b8: Add consent settings, consent/PII validation, and protected resources.

    • gtm.tags.*.consent and events.*.consent map to GTM's per-tag consentSettings, and a bare
      consentInit trigger type is now supported for firing a default-consent tag before everything
      else.
    • Validation now fails when a ga4Event/googleTag tag, or an events.* entry (which compiles
      to one), has no consent block, and when an event parameter name suggests personal data
      (email, phone, address, and similar).
    • protected: true on a GTM resource requires --allow-destroy-protected, on top of
      --allow-destroy, before apply deletes it. GA4 resources aren't covered yet.

@kisztof
kisztof merged commit d06cb43 into main Aug 28, 2026
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.

1 participant