v2.5.0

2.5.0 (2026-01-23)

Features

• Provide access to HTTP headers on connect or error (#77) (b50d660)

---

This PR was generated with Release Please. See documentation.

v2.4.0

2.4.0 (2026-01-15)

Features

• Support dynamic query parameter on reconnect (#74) (e6c76bf)

---

This PR was generated with Release Please. See documentation.

v2.3.0

2.3.0 (2025-08-28)

Features

• Add ability to control SSE request method and body (#51) (7c65c4b)
• Add ability to disable retries (#67) (f272b90)
• Allow providing HTTP client option settings (#68) (1d9b31c)

Bug Fixes

• Handle redirect on 301 and 307 (7d342e7)
• Pass through proxy user and password if present (#69) (0bb36f3)
• Support field without colon in event (7d342e7)

v2.2.6

2.2.6 (2025-07-15)

Bug Fixes

• Add logger as explicit dependency (#61) (50efb0d)
• Update force_encoding to operate on unfrozen string (#60) (0e2e80d)

v2.2.5

2.2.5 (2025-07-14)

Bug Fixes

• Bump minimum to ruby 3.1 (#57) (93a9947)
• Explicitly mark buffer variable as unfrozen (#59) (ccf79af)

v2.2.4

2.2.4 (2025-04-18)

Bug Fixes

• Remove rake dependency from gemspec (#53) (8be0ccc)

v2.2.3

2.2.3 (2025-03-07)

Bug Fixes

• Provide thread name for inspection (#46) (191fd68)

2.2.2

[2.2.2] - 2023-03-13

Fixed:

• Content-Type checking was failing in some environments due to casing issues. Updated check to use a more robust header retrieval method. (Thanks, matt-dutchie!)

2.2.1

[2.2.1] - 2022-06-15

Fixed:

• Improved efficiency of SSE parsing to reduce transient memory/CPU usage spikes when streams contain long lines. (Thanks, sq-square!)

2.2.0

[2.2.0] - 2021-12-31

Added:

• The StreamEvent type now has a new property, last_event_id. Unlike the id property which reports only the value of the id: field (if any) in that particular event, last_event_id reports the id: value that was most recently specified in any event. The specification states that this state should be included in every event; the ability to distinguish last_event_id from id is an extended feature of this gem.

Fixed:

• The client could stop reading the stream and return an error if there was a multi-byte UTF-8 character whose bytes were split across two reads. It now handles this correctly.
• In JRuby only, the client returned an error when trying to reconnect a stream if the initial reconnect delay was set to zero.
• As per the specification, the parser now ignores any id: field whose value contains a null (zero byte).
• The last event ID that is sent in the Last-Event-Id header was only being updated if an event specified a non-empty value for id:. As per the specification, it should be possible to explicitly clear this value by putting an empty id: field in an event.