Releases: launchdarkly/ruby-eventsource
Releases · launchdarkly/ruby-eventsource
2.0.1
[2.0.1] - 2021-08-10
Changed:
- The dependency version constraint for the
http
gem is now looser: it allows 5.x versions as well as 4.x. The breaking changes inhttp
v5.0.0 do not affectld-eventsource
. - The project's build now uses v2.2.10 of
bundler
due to known vulnerabilities in other versions. Gemfile.lock
has been removed from source control. As this is a library project, the lockfile never affected application code that used this gem, but only affected the gem's own CI build. It is preferable for the CI build to refer only to the gemspec so that it resolves dependencies the same way an application using this gem would, rather than using pinned dependencies that an application would not use.
2.0.0
[2.0.0] - 2021-01-26
Added:
- Added a
socket_factory
configuration option which can be used for socket creation by the HTTP client if provided. The value ofsocket_factory
must be an object providing anopen(uri, timeout)
method and returning a connected socket.
Changed:
- Switched to the
http
gem instead ofsocketry
and a custom HTTP client. - Dropped support for Ruby < version 2.5
- Dropped support for JRuby < version 9.2
1.0.3
[1.0.3] - 2020-03-17
Fixed:
- The backoff delay logic for reconnecting after a stream failure was broken so that if a failure occurred after a stream had been active for at least
reconnect_reset_interval
(default 60 seconds), retries would use no delay, potentially causing a flood of requests and a spike in CPU usage.
1.0.2
[1.0.2] - 2020-03-10
Removed:
- Removed an unused dependency on
rake
. There are no other changes in this release.
1.0.1
Fixed:
- Calling
close
on the client could cause a misleading warning message in the log, such asUnexpected error from event source: #<IOError: stream closed in another thread>
.
1.0.0
[1.0.0] - 2019-01-03
Initial release.