Releases: segmentio/analytics-next
Releases · segmentio/analytics-next
@segment/[email protected]
@segment/[email protected]
@segment/[email protected]
@segment/[email protected]
@segment/[email protected]
What's Changed
- Fix schema filter name collision bug by @danieljackins in #1036
- Non-blocking lazy destinations by @zikaari in #945
- Allow custom metrics endpoint by @danieljackins in #1037
@segment/[email protected]
@segment/[email protected]
Major Changes
- #935
833ade8
Thanks @MichaelGHSeg! - Removing support for Node.js 14 and 16 as they are EOL
-
#935
833ade8
Thanks @MichaelGHSeg! - Support for Segment OAuth2OAuth2 must be enabled from the Segment dashboard. You will need a PEM format
private/public key pair. Once you've uploaded your public key, you will need
the OAuth Client Id, the Key Id, and your private key. You can set these in
the new OAuthSettings type and provide it in your Analytics configuration.Note: This introduces a breaking change only if you have implemented a custom
HTTPClient. HTTPClientRequestdata: Record<string, any>
has changed to
body: string
. Processing data into a string now occurs before calls to
makeRequest
@segment/[email protected]
@segment/[email protected]
@segment/[email protected]
Minor Changes
- #1015
8fbe1a0
Thanks @silesky! - DeprecatemaxEventsInBatch
in favor of our commonly used:flushAt
. The purpose is to establish consistency between our SDKs, regardless of language.
Patch Changes
- Updated dependencies [
7b93e7b
]:- @segment/[email protected]
- @segment/[email protected]