Sync with upstream v2.2.6 + enhanced features#7
Merged
Conversation
…unchdarkly#36) In some environments, retrieving the `content-type` header directly from the headers hash was returning an empty string. In those environments, the header was stored as `Content-Type`. By updating the code to use the provided `content_type` method provided on the response object, we can shield ourselves from casing issues like this in the future.
🤖 I have created a release *beep* *boop* --- ## [2.2.3](launchdarkly/ruby-eventsource@2.2.2...2.2.3) (2025-03-07) ### Bug Fixes * Provide thread name for inspection ([launchdarkly#46](launchdarkly#46)) ([191fd68](launchdarkly@191fd68)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
🤖 I have created a release *beep* *boop* --- ## [2.2.4](launchdarkly/ruby-eventsource@2.2.3...2.2.4) (2025-04-18) ### Bug Fixes * Remove rake dependency from gemspec ([launchdarkly#53](launchdarkly#53)) ([8be0ccc](launchdarkly@8be0ccc)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
In a future version of Ruby, literal strings will be frozen by default. To avoid this causing an issue (and raising deprecation warnings now), we are explicitly marking this literal string as unfrozen.
🤖 I have created a release *beep* *boop* --- ## [2.2.5](launchdarkly/ruby-eventsource@2.2.4...2.2.5) (2025-07-14) ### Bug Fixes * Bump minimum to ruby 3.1 ([launchdarkly#57](launchdarkly#57)) ([93a9947](launchdarkly@93a9947)) * Explicitly mark buffer variable as unfrozen ([launchdarkly#59](launchdarkly#59)) ([ccf79af](launchdarkly@ccf79af)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Starting in 3.5.0, `logger` will no longer be a part of the default gems. v1.5 of the logger was shipped with Ruby 3.1.0, so this should maintain equivalent functionality.
🤖 I have created a release *beep* *boop* --- ## [2.2.6](launchdarkly/ruby-eventsource@2.2.5...2.2.6) (2025-07-15) ### Bug Fixes * Add `logger` as explicit dependency ([launchdarkly#61](launchdarkly#61)) ([50efb0d](launchdarkly@50efb0d)) * Update `force_encoding` to operate on unfrozen string ([launchdarkly#60](launchdarkly#60)) ([0e2e80d](launchdarkly@0e2e80d)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
- Add support for POST/PUT HTTP methods with JSON payload - Fix proxy authentication parameter names (proxy_username/proxy_password) - Add optional parsing mode to bypass SSE parsing for raw data streaming These changes enable more flexible usage patterns while maintaining backward compatibility with existing GET-only SSE implementations.
Add verify_ssl parameter (defaults to true) to allow disabling SSL certificate verification for development, testing, and internal networks. This maintains security by default while providing flexibility when needed.
Remove extra empty line at class body beginning in BasicEventParser.
jefferson-surge
approved these changes
Sep 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
9 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR syncs our fork with the latest upstream LaunchDarkly release (v2.2.6) and includes our enhanced features:
Upstream Changes (v2.2.6)
Our Enhanced Features
proxy_username/proxy_password)Compatibility
All changes maintain backward compatibility. Existing code continues to work unchanged since all new parameters have sensible defaults.
Test Status