Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable specific_platform by default #4015

Merged
merged 2 commits into from Nov 12, 2020

Commits on Nov 12, 2020

  1. Enable specific_platform by default

    To properly support gems providing native platform versions with
    different dependencies than their pure ruby counterparts.
    
    Nokogiri will start doing this soon. In particular, for each version,
    the pure ruby variant will not have a `required_ruby_version` upper
    bound, but the native variant will. Bundler should always install a
    valid bundle in this case.
    deivid-rodriguez committed Nov 12, 2020
    Copy the full SHA
    0bcf749 View commit details
    Browse the repository at this point in the history
  2. Probably better fix to previous issue

    With specific platforms by default, it sounds like we can fix a
    previous "duplicated spec groups" issue by calling uniq on the array of
    definition platforms.
    deivid-rodriguez committed Nov 12, 2020
    Copy the full SHA
    91cfcfe View commit details
    Browse the repository at this point in the history