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

Don't consider platform specific candidates when force_ruby_platform set #6442

Merged
merged 1 commit into from
Mar 9, 2023

Conversation

deivid-rodriguez
Copy link
Member

What was the end-user or developer problem that led to this PR?

This was working fine for direct dependencies using force_ruby_platform explicitly through Gemfile, but not for indirect dependencies. In general, indirect dependencies do not have this property set, but in truffleruby this is different and the default value is to have it set.

What is your fix for the problem, implemented in this PR?

Consider force_ruby_platform when finding resolution candidates for indirect dependencies.

Fixes #6435.

Make sure the following tasks are checked

@deivid-rodriguez deivid-rodriguez changed the title Don´t consider platform specific candidates when force_ruby_platform set Don't consider platform specific candidates when force_ruby_platform set Mar 7, 2023
…` set

This was working fine for direct dependencies using
`force_ruby_platform` explicitly through Gemfile, but not for indirect
dependencies. In general, indirect dependencies do not have this
property set, but in truffleruby this is different and the default value
is to have it set.
@deivid-rodriguez deivid-rodriguez marked this pull request as ready for review March 7, 2023 18:51
@deivid-rodriguez deivid-rodriguez added this pull request to the merge queue Mar 9, 2023
Merged via the queue into master with commit d0c6de9 Mar 9, 2023
@deivid-rodriguez deivid-rodriguez deleted the fix-locking-specs-on-truffleruby branch March 9, 2023 18:52
deivid-rodriguez added a commit that referenced this pull request Mar 20, 2023
Don't consider platform specific candidates when `force_ruby_platform` set

(cherry picked from commit d0c6de9)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bundler 2.4.0 and later, on truffleruby, when using gemspec, misses gems
1 participant