fix: Explicitly require openssl gem #334
Merged
Conversation
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
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
jsonbailey
approved these changes
Oct 9, 2025
keelerm84
force-pushed
the
mk/sdk-1491/openssl
branch
2 times, most recently
from
869defd to
8b8730d
Compare
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
|
@keelerm84 Thanks for this PR. I’ve been struggling with this issue since yesterday and finally resolved it by adding gem "openssl", "~> 3.3" |
OpenSSL 3.6.0 introduced a change in behavior which prevents the SDK from initializing. To learn more, refer to [this github ticket][1]. To mitigate this, we explicitly depend on the openssl gem instead of loading the default version shipped with Ruby. This SDK still advertises Ruby 3.1+ support, which should require a minimum threshold of openssl-v3.0+. However, Ruby 3.1 is EOL and the openssl maintainer only implemented fixes in openssl-v3.1+. Thus, we set the minimum to openssl-v3.1. [1]: ruby/openssl#949 fixes #333
keelerm84
force-pushed
the
mk/sdk-1491/openssl
branch
from
8b8730d to
fefbbb8
Compare
keelerm84
pushed a commit
that referenced
this pull request
Oct 10, 2025
🤖 I have created a release *beep* *boop* --- ## [8.11.1](8.11.0...8.11.1) (2025-10-10) ### Bug Fixes * Explicitly require openssl gem ([#334](#334)) ([0ea53a5](0ea53a5)), closes [#333](#333) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). <!-- CURSOR_SUMMARY --> --- > [!NOTE] > Release 8.11.1 with a bug fix to explicitly require the openssl gem, updating version metadata and provenance docs. > > - **Release 8.11.1** > - Update version to `8.11.1` in `.release-please-manifest.json` and `lib/ldclient-rb/version.rb`. > - Add CHANGELOG entry for bug fix: explicitly require `openssl` gem. > - Update `PROVENANCE.md` example to use `SDK_VERSION=8.11.1`. > > <sup>Written by [Cursor Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit 8586552. This will update automatically on new commits. Configure [here](https://cursor.com/dashboard?tab=bugbot).</sup> <!-- /CURSOR_SUMMARY --> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
OpenSSL 3.6.0 introduced a change in behavior which prevents the SDK
from initializing. To learn more, refer to this github ticket.
To mitigate this, we explicitly depend on the openssl gem instead of
loading the default version shipped with Ruby.
This SDK still advertises Ruby 3.1+ support, which should require a
minimum threshold of openssl-v3.0+. However, Ruby 3.1 is EOL and the
openssl maintainer only implemented fixes in openssl-v3.1+. Thus, we set
the minimum to openssl-v3.1.
fixes #333
Note
Add explicit
opensslruntime dependency (~> 3.1,>= 3.1.2) inlaunchdarkly-server-sdk.gemspec.Written by Cursor Bugbot for commit fefbbb8. This will update automatically on new commits. Configure here.