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/[email protected]
Patch Changes
7072377
Thanks @danieljackins! - Fix batching after page navigation@segment/[email protected]
Patch Changes
#912
70cc6e6
Thanks @silesky! - Support classic destinations and locally installed action destinations by removing integrations.#918
fd0862c
Thanks @silesky! - Remove default behavior that prunes unmapped categories from context.contest payload. As such, by default,allKeys
will no longer be used. Add ability to turn pruning back on via anpruneUnmappedCategories
setting.@segment/[email protected]
Patch Changes
#919
e3e3971
Thanks @silesky! - Require category IDs for OneTrust mapping (e.g CAT0002, SEG0003), and do not accept category name any more. Reason: documentation is easier, and Segment currently has a 20 char limit on category IDs.Updated dependencies [
70cc6e6
,fd0862c
]: