Skip to content

πŸ¦‹ New version release - #7

Merged
brentrager merged 1 commit into
mainfrom
changeset-release/main
May 18, 2026
Merged

πŸ¦‹ New version release#7
brentrager merged 1 commit into
mainfrom
changeset-release/main

Conversation

@brentrager

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@smooai/observability@0.4.0

Minor Changes

  • 365b90c: OTel-first node Client (SMOODEV-1067d).

    The Node Client no longer wraps a Smoo-native HTTP transport β€” it emits to OpenTelemetry natively. Every captureException / captureMessage becomes a span event on the active OTel span (or a synthetic one if none is active), with SpanStatusCode.ERROR for exceptions and OTLP-shaped attributes (enduser.id, enduser.org_id, service.version, deployment.environment.name, smoo.tag.*, smoo.event_id, smoo.level). The OTel SDK handles batching, retry, and wire format; the Smoo SDK does not run a parallel HTTP pipeline on Node.

    @smooai/logger is now optional. The Smoo SDK has no compile-time dependency on it. When present, its CONTEXT global feeds OTel baggage (see @smooai/observability-otel). When absent, the OTel ambient context (W3C trace context propagation, baggage) is the single source of correlation truth β€” winston / pino / bunyan / console users get the same trace-id flowing through logs, traces, and Smoo error groups by reading readOtelCorrelation().

    Breaking changes (@smooai/observability 0.3 β†’ 0.4):

    • makeNodeTransport (re-exported from the node entry) removed β€” no longer needed; OTel SDK is the transport.

    • Client._registerTransport is now a no-op on Node when a capture handler is registered (which happens by default in Client.init). Browser is unchanged.

    • New seam Client._registerCaptureHandler(handler | null) for advanced consumers who want to plug in their own non-OTel capture path.

      Breaking changes (@smooai/observability-otel 0.1 β†’ 0.2):

    • bridgeClientToOtel() removed. There's nothing to bridge β€” the Smoo Client already emits to OTel natively on Node. setupOtelSdk() and readOtelCorrelation() remain.

      Tests: 33 green on core (was 24), 5 on otel package. Typecheck + build clean.

@smooai/observability-otel@0.3.0

Minor Changes

  • 365b90c: OTel-first node Client (SMOODEV-1067d).

    The Node Client no longer wraps a Smoo-native HTTP transport β€” it emits to OpenTelemetry natively. Every captureException / captureMessage becomes a span event on the active OTel span (or a synthetic one if none is active), with SpanStatusCode.ERROR for exceptions and OTLP-shaped attributes (enduser.id, enduser.org_id, service.version, deployment.environment.name, smoo.tag.*, smoo.event_id, smoo.level). The OTel SDK handles batching, retry, and wire format; the Smoo SDK does not run a parallel HTTP pipeline on Node.

    @smooai/logger is now optional. The Smoo SDK has no compile-time dependency on it. When present, its CONTEXT global feeds OTel baggage (see @smooai/observability-otel). When absent, the OTel ambient context (W3C trace context propagation, baggage) is the single source of correlation truth β€” winston / pino / bunyan / console users get the same trace-id flowing through logs, traces, and Smoo error groups by reading readOtelCorrelation().

    Breaking changes (@smooai/observability 0.3 β†’ 0.4):

    • makeNodeTransport (re-exported from the node entry) removed β€” no longer needed; OTel SDK is the transport.

    • Client._registerTransport is now a no-op on Node when a capture handler is registered (which happens by default in Client.init). Browser is unchanged.

    • New seam Client._registerCaptureHandler(handler | null) for advanced consumers who want to plug in their own non-OTel capture path.

      Breaking changes (@smooai/observability-otel 0.1 β†’ 0.2):

    • bridgeClientToOtel() removed. There's nothing to bridge β€” the Smoo Client already emits to OTel natively on Node. setupOtelSdk() and readOtelCorrelation() remain.

      Tests: 33 green on core (was 24), 5 on otel package. Typecheck + build clean.

Patch Changes

  • Updated dependencies [365b90c]
    • @smooai/observability@0.4.0

@smooai/observability-next@0.4.0

Patch Changes

  • Updated dependencies [365b90c]
    • @smooai/observability@0.4.0
    • @smooai/observability-react@0.4.0

@smooai/observability-react@0.4.0

Patch Changes

  • Updated dependencies [365b90c]
    • @smooai/observability@0.4.0

@brentrager
brentrager force-pushed the changeset-release/main branch from 3efefde to a1a6ff8 Compare May 18, 2026 14:20
@brentrager
brentrager merged commit 90a9ee3 into main May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant