feat(gemset): Install gems per Ruby version to avoid compat issues #231
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.
When users switch Ruby versions (e.g., from 3.2 to 3.3), previously installed gems with native extensions can break due to ABI incompatibilities or something else. This also affects the same Ruby version compiled with different configurations or on different platforms.
This change introduces version-specific gem directories by hashing the output of
ruby --version, which includes version, revision, and platform info. Gems are now installed togems/<hash>/instead of the extension root, ensuring each Ruby environment gets its own isolated gem set.Closes #107