This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@segment/analytics-next@1.69.0
Minor Changes
#1080e884b61 Thanks @silesky! - Addresses an issue where, if one of the non-destination actions fails to load/is blocked, the entire SDK fails to load. This is most notable in GA4, where, if GA was blocked, Segment initialization would fail.
#1080e884b61 Thanks @silesky! - Addresses an issue where, if one of the non-destination actions fails to load/is blocked, the entire SDK fails to load. This is most notable in GA4, where, if GA was blocked, Segment initialization would fail.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
@segment/analytics-next@1.69.0
Minor Changes
e884b61
Thanks @silesky! - Addresses an issue where, if one of the non-destination actions fails to load/is blocked, the entire SDK fails to load. This is most notable in GA4, where, if GA was blocked, Segment initialization would fail.Patch Changes
e884b61
,e884b61
]:@segment/analytics-core@1.6.0
Minor Changes
#1080
e884b61
Thanks @silesky! - Do not throw errors in .register() method.#1080
e884b61
Thanks @silesky! - Addresses an issue where, if one of the non-destination actions fails to load/is blocked, the entire SDK fails to load. This is most notable in GA4, where, if GA was blocked, Segment initialization would fail.@segment/analytics-node@2.1.2
Patch Changes
e884b61
,e884b61
]: