@segment/analytics-node@3.1.0

Minor Changes

• #1342 65951526 Thanks @MichaelGHSeg! - Unify and harden HTTP response handling and retry behavior across browser and node SDKs.

  • Browser (@segment/analytics-next) - Add config-driven response handling for Segment.io delivery (httpConfig with rate-limit/backoff controls). - Improve batching/dispatcher retry semantics for 429 and transient failures. - Use configured protocol for batching requests when apiHost has no scheme, while preserving compatibility for apiHost values that already include http:// or https://.

  • Node (@segment/analytics-node) - Align publisher retry/status behavior with updated response handling rules. - Add maxTotalBackoffDuration and maxRateLimitDuration settings to control retry ceilings. - Update default retry configuration to increase resilience under transient failures.

  • Core (@segment/analytics-core) - Standardize backoff defaults used by retry queues.

Patch Changes

• #1365 5eb12a17 Thanks @MichaelGHSeg! - Fix closeAndFlush silently dropping in-flight events on timeout.

  • Cancel pending retry sleeps via AbortController when closeAndFlush times out, instead of silently swallowing the timeout error.
  • Raise default closeAndFlush timeout floor to 75s (was 12.5s) so it survives at least one Retry-After: 60 cycle.
  • Add http_response emitter event for observing API response status codes and headers.

• Updated dependencies [65951526]:

  • @segment/analytics-core@1.8.3

@segment/analytics-next@1.84.0

Minor Changes

• #1342 65951526 Thanks @MichaelGHSeg! - Unify and harden HTTP response handling and retry behavior across browser and node SDKs.

  • Browser (@segment/analytics-next) - Add config-driven response handling for Segment.io delivery (httpConfig with rate-limit/backoff controls). - Improve batching/dispatcher retry semantics for 429 and transient failures. - Use configured protocol for batching requests when apiHost has no scheme, while preserving compatibility for apiHost values that already include http:// or https://.

  • Node (@segment/analytics-node) - Align publisher retry/status behavior with updated response handling rules. - Add maxTotalBackoffDuration and maxRateLimitDuration settings to control retry ceilings. - Update default retry configuration to increase resilience under transient failures.

  • Core (@segment/analytics-core) - Standardize backoff defaults used by retry queues.

Patch Changes

• Updated dependencies [65951526]:
  • @segment/analytics-core@1.8.3

@segment/analytics-core@1.8.3

Patch Changes

• #1342 65951526 Thanks @MichaelGHSeg! - Unify and harden HTTP response handling and retry behavior across browser and node SDKs.

  • Browser (@segment/analytics-next) - Add config-driven response handling for Segment.io delivery (httpConfig with rate-limit/backoff controls). - Improve batching/dispatcher retry semantics for 429 and transient failures. - Use configured protocol for batching requests when apiHost has no scheme, while preserving compatibility for apiHost values that already include http:// or https://.

  • Node (@segment/analytics-node) - Align publisher retry/status behavior with updated response handling rules. - Add maxTotalBackoffDuration and maxRateLimitDuration settings to control retry ceilings. - Update default retry configuration to increase resilience under transient failures.

  • Core (@segment/analytics-core) - Standardize backoff defaults used by retry queues.

@segment/analytics-next@1.83.0

Minor Changes

• #1356 bd498512 Thanks @laksh-twilio! - Fixes #1336 NullAnalytics was accidentally removed from the public exports in commit b611746 (PR #1090) when exports were changed from wildcard to explicit. This restores the export for users who need NullAnalytics in their test code.

Patch Changes

• #1357 a70d9e69 Thanks @chenxzhang! - Rename middleware chunk name to avoid collision with Next.js middleware entrypoint

@segment/analytics-next@1.82.0

Minor Changes

• #1350 d41ca131 Thanks @mschasz! - Upgrade AWS SDK from v2 to v3 in browser release script.

@segment/analytics-node@3.0.0

Major Changes

• #1348 99cd853b Thanks @MichaelGHSeg! - Remove node-fetch dependency in favor of native globalThis.fetch (available since Node 18, package requires >= 20)

@segment/analytics-next@1.81.2

Patch Changes

• #1341 6477267f Thanks @MichaelGHSeg! - Emit analytics_js.integration.invoke.error metric for destination load and build failures that were previously silent

@segment/analytics-consent-wrapper-onetrust@1.1.3

Patch Changes

• Updated dependencies [1e269614]:
  • @segment/analytics-consent-tools@2.0.3

@segment/analytics-consent-tools@2.0.3

Patch Changes

• #1328 1e269614 Thanks @chenxzhang! - Fix filtering of non-consented integrations

@segment/analytics-node@2.3.0

Minor Changes

• #1307 5ae083f4 Thanks @neelkanth-kaushik! - # Updated Node.js version to ^20 across the repository

  Files modified:

  1. .github/workflows/ci.yml
  2. package.json
  3. packages/node/package.json

Patch Changes

• Updated dependencies [5b6bdd92]:
  • @segment/analytics-core@1.8.2