Releases: launchdarkly/ruby-eventsource
Releases · launchdarkly/ruby-eventsource
v2.6.0
Compare
Sorry, something went wrong.
No results found
Immutable
release. Only release title and notes can be modified.
2.6.0 (2026-03-26)
Features
Expand version support for http.rb v6 (#82 ) (2f8732a )
This PR was generated with Release Please . See documentation .
v2.5.1
Compare
Sorry, something went wrong.
No results found
2.5.1 (2026-03-02)
Bug Fixes
Use in-place append for buffer concatenation to fix O(n^2) performance (#80 ) (a7e6c23 )
This PR was generated with Release Please . See documentation .
v2.5.0
Compare
Sorry, something went wrong.
No results found
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.3.0
Compare
Sorry, something went wrong.
No results found
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
Compare
Sorry, something went wrong.
No results found
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
Compare
Sorry, something went wrong.
No results found
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
Compare
Sorry, something went wrong.
No results found
2.2.4 (2025-04-18)
Bug Fixes
Remove rake dependency from gemspec (#53 ) (8be0ccc )
v2.2.3
Compare
Sorry, something went wrong.
No results found
2.2.3 (2025-03-07)
Bug Fixes
Provide thread name for inspection (#46 ) (191fd68 )
2.2.2
Compare
Sorry, something went wrong.
No results found
[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 !)