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 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.65.0
Minor Changes
d212633
Thanks @zikaari! - Load destinations lazily and start sending events as each becomes available instead of waiting for all to load firstPatch Changes
#1036
f65c131
Thanks @danieljackins! - Fix schema-filter bugUpdated dependencies [
95fd2fd
,d212633
]:@segment/analytics-core@1.5.0
Minor Changes
d212633
Thanks @zikaari! - Load destinations lazily and start sending events as each becomes available instead of waiting for all to load firstPatch Changes
#1043
95fd2fd
Thanks @silesky! - This ensures backward compatibility with analytics-node by modifying '@segment/analytics-core'. Specifically, the changes prevent the generation of a messageId if it is already set. This adjustment aligns with the behavior outlined in analytics-node's source code here.While this is a core release, only the node library is affected, as the browser has its own EventFactory atm.
Updated dependencies [
d212633
]:@segment/analytics-generic-utils@1.2.0
Minor Changes
d212633
Thanks @zikaari! - Load destinations lazily and start sending events as each becomes available instead of waiting for all to load first@segment/analytics-node@2.1.0
Minor Changes
#1043
95fd2fd
Thanks @silesky! - This ensures backward compatibility with analytics-node by modifying '@segment/analytics-core'. Specifically, the changes prevent the generation of a messageId if it is already set. This adjustment aligns with the behavior outlined in analytics-node's source code here.While this is a core release, only the node library is affected, as the browser has its own EventFactory atm.
Patch Changes
95fd2fd
,d212633
]: