v1.11.0

1.11.0 (2025-11-20)

Features

• Support SSE server with event limited jitter support (#58) (7b0f448)

Bug Fixes

• Bump gopkg.in/yaml.v3 from 3.0.0 to 3.0.1 (#55) (7c0d519)

v1.10.0

1.10.0 (2025-07-01)

Features

• Add header support (#53) (b3a725f)

v1.9.1

1.9.1 (2025-06-02)

Bug Fixes

• Prevent close on a nil channel (#49) (efc49c6)

v1.9.0

1.9.0 (2025-04-21)

Features

• Include response headers in subscription errors (#46) (271f33d)

v1.8.0

1.8.0 (2024-12-19)

Features

• Add ability to provide dynamic query parameters (#44) (efc5d86)

v1.7.1

[1.7.1] - 2022-05-10

Fixed:

• In the SSE server implementation, removed string concatenation logic that caused writing of large messages to be unnecessarily memory-intensive. (Thanks, moshegood!)
• The SSE server implementation did not correctly write a message if the data field was empty: it dropped the field entirely, which would cause clients not to read the message.

1.7.0

[1.7.0] - 2022-01-05

This release includes improvements for SSE spec compliance that do not affect usage in the LaunchDarkly Go SDK, but may be relevant in other use cases.

Added:

• Each event returned by the client now includes the last event ID that was seen on this stream (if any), rather than only the ID (if any) that was in that particular event. This is a requirement of the SSE spec. For backward compatibility, Event.Id() still has the old behavior of returning only the ID for that event; the new behavior is in a new interface method, EventWithLastID.LastEventID(). Every event returned by the client implements both Event and EventWithLastID.

Changed:

• CI tests now use the latest v2 release of https://github.com/launchdarkly/sse-contract-tests.

Fixed:

• The client should discard any id: field that contains a null character, as per the SSE spec.

1.6.2

[1.6.2] - 2020-12-02

Fixed:

• Removed extra newline from "Reconnecting in..." log message.

1.6.1

[1.6.1] - 2020-07-23

Changed:

• Server.Handler() now uses the standard context.Context mechanism to detect when a request has been cancelled, instead of the deprecated http.CloseNotifier.

1.6.0

[1.6.0] - 2020-07-23

Added:

• Server.Unregister method for removing a Repository registration and optionally forcing clients to disconnect.
• Server.PublishWithAcknowledgement method for ensuring that an action does not happen until an event has been dispatched.

Fixed:

• Fixed a race condition in which Server might close a channel while another goroutine is trying to write to it. This would happen if you registered a Repository that replays events, started a handler, then closed the Server while the events were still replaying.
• Improved unit test coverage.