Document gemspecs must be deterministic#9321
Merged
Merged
Conversation
4 tasks
hsbt
approved these changes
Feb 9, 2026
hsbt
added a commit
that referenced
this pull request
Feb 24, 2026
Document gemspecs must be deterministic (cherry picked from commit 895f384)
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.
What was the end-user or developer problem that led to this PR?
After the #8879, I wondered if I could ship a C extension whose
extconf.rbwas hidden forGem::VERSIONs not supporting that feature.I learned from @eregon that is not possible.
What is your fix for the problem, implemented in this PR?
Document this detail.
Make sure the following tasks are checked