Fix OpenSSL mismatch vs Ruby 3.4 default causing build failure#181
Merged
Conversation
Andrew Kent (realark)
approved these changes
Jun 9, 2026
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
2 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.
Problem
We specified
opensslin the gemspec, which happens to be a default gem packaged with Ruby.During our build/release process, if Ruby uses/loads
opensslwithRUBYOPTbefore Bundler, its possible to have an "already loaded" version mismatch where the default gem version doesn't match the one installed by Bundler. This leads to build failures.Solution
Bump our CI Ruby version to 4.0 and pin our
Gemfileto a version ofopensslthat specifically matches a known version of the Ruby runner in CI. This only affects our local build tooling (doesn't prevent users from using neweropensslversions), but does require us to keep this in sync with our Ruby version used in CI.