Release - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.8.0
Minor Changes
2d02443: Adds
ga4.measurementProtocolSecretsas a stream-scoped create/update/delete resource (config keyis the secret's
displayName;secretValueis server-generated and never in config). Creating onerequires the property's User Data Collection Acknowledgement to already be attested through the GA4
UI.
applysurfaces GA4'sFAILED_PRECONDITIONwith a remediation hint naming that requirement.google.ga4.measurementIdno longer has to be set by hand:plan/apply/driftnow derive it fromga4.streamWebsiteUrl's resolved web stream when config leaves it unset.iOS/Android GA4 data streams are confirmed not implementable through the Admin API (it refuses
creation outright, directing callers to the Firebase API instead) and are documented as a hard
blocker rather than left as an open roadmap item.
31be5a4: Adds
ga4.attributionSettings(reportingAttributionModel,acquisitionConversionEventLookbackWindow,otherConversionEventLookbackWindow) as aproperty-level, settings-diffed field, following the same pattern as
dataRetentionandgoogleSignals:plan/driftcompare it against the property's live state andapplyPATCHesonly the fields that changed.
Internal and developer traffic filters are confirmed not implementable through the GA4 Admin
API: no
dataFilters-shaped collection exists under eitherv1alphaorv1beta. Documented as ahard blocker in README and ROADMAP, the same way iOS/Android data streams and Search Console links
already are. This closes out 0.7's GA4 coverage milestone.