@effect-messaging/nats@0.7.1

Patch Changes

• #120 d439eed Thanks @wewelll! - Fix error span attributes for Datadog error tracking

  • Changed tag to _tag property check to correctly extract error type from Effect's TaggedError
  • Wrapped Cause.squashWith calls in String() to ensure span attributes are always strings
  • This ensures error.type, error.message, and error.stack are properly set for Datadog error tracking

@effect-messaging/amqp@0.5.1

Patch Changes

• #120 d439eed Thanks @wewelll! - Fix error span attributes for Datadog error tracking

  • Changed tag to _tag property check to correctly extract error type from Effect's TaggedError
  • Wrapped Cause.squashWith calls in String() to ensure span attributes are always strings
  • This ensures error.type, error.message, and error.stack are properly set for Datadog error tracking

@effect-messaging/nats@0.7.0

Minor Changes

• #115 2b26c0d Thanks @wewelll! - Add subscriber response types for explicit message acknowledgment control

  • Added response type parameter to Subscriber interface in core
  • Added AMQPSubscriberResponse module with Ack, Nack, and Reject response types
  • Added JetStreamSubscriberResponse module with Ack, Nak, and Term response types
  • Subscribers now return a response to control message acknowledgment behavior
  • On handler error, messages are still nacked/rejected automatically

Patch Changes

• Updated dependencies [2b26c0d]:
  • @effect-messaging/core@0.2.39

@effect-messaging/core@0.2.39

Patch Changes

• #115 2b26c0d Thanks @wewelll! - Add subscriber response types for explicit message acknowledgment control

  • Added response type parameter to Subscriber interface in core
  • Added AMQPSubscriberResponse module with Ack, Nack, and Reject response types
  • Added JetStreamSubscriberResponse module with Ack, Nak, and Term response types
  • Subscribers now return a response to control message acknowledgment behavior
  • On handler error, messages are still nacked/rejected automatically

@effect-messaging/amqp@0.5.0

Minor Changes

• #115 2b26c0d Thanks @wewelll! - Add subscriber response types for explicit message acknowledgment control

  • Added response type parameter to Subscriber interface in core
  • Added AMQPSubscriberResponse module with Ack, Nack, and Reject response types
  • Added JetStreamSubscriberResponse module with Ack, Nak, and Term response types
  • Subscribers now return a response to control message acknowledgment behavior
  • On handler error, messages are still nacked/rejected automatically

Patch Changes

• Updated dependencies [2b26c0d]:
  • @effect-messaging/core@0.2.39

@effect-messaging/nats@0.6.1

Patch Changes

• #113 5f72eba Thanks @wewelll! - upgrade effect libraries to their latest version

• Updated dependencies [5f72eba]:

  • @effect-messaging/core@0.2.38

@effect-messaging/core@0.2.38

Patch Changes

• #113 5f72eba Thanks @wewelll! - upgrade effect libraries to their latest version

@effect-messaging/amqp@0.4.40

Patch Changes

• #113 5f72eba Thanks @wewelll! - upgrade effect libraries to their latest version

• Updated dependencies [5f72eba]:

  • @effect-messaging/core@0.2.38

@effect-messaging/nats@0.6.0

Minor Changes

• #111 e6dd444 Thanks @wewelll! - Add NATSPublisher and NATSSubscriber for NATS Core (without JetStream)

  • NATSPublisher: Implements the Publisher interface from @effect-messaging/core using NATS Core publish (fire-and-forget)
  • NATSSubscriber: Implements the Subscriber interface from @effect-messaging/core using NATS Core subscriptions
  • Both include OpenTelemetry tracing with distributed trace context propagation via headers
  • NATSSubscriber supports uninterruptible and handlerTimeout options
  • Note: NATS Core has no persistence - messages published before subscription starts are lost

@effect-messaging/nats@0.5.2

Patch Changes

• #108 1bd9628 Thanks @wewelll! - Upgrade @nats-io/jetstream, @nats-io/nats-core, and @nats-io/transport-node to 3.3.0