You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The gem does not install via Rubygems due to a compatibility error.
Steps to reproduce the error:
Create new app: rails new test_app
Add gem 'active_record_upsert' to Gemfile
bundle
bundle
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
Could not find compatible versions
Because rails >= 7.2.2.1, < 8.0.0.beta1 depends on activerecord = 7.2.2.1
and rails >= 7.2.2, < 7.2.2.1 depends on activerecord = 7.2.2,
rails >= 7.2.2, < 8.0.0.beta1 requires activerecord = 7.2.2 OR = 7.2.2.1.
And because rails >= 7.2.1.2, < 7.2.2 depends on activerecord = 7.2.1.2,
rails >= 7.2.1.2, < 8.0.0.beta1 requires activerecord = 7.2.1.2 OR = 7.2.2 OR = 7.2.2.1.
(1) So, because rails >= 7.2.1.1, < 7.2.1.2 depends on activerecord = 7.2.1.1
and rails >= 7.2.1, < 7.2.1.1 depends on activerecord = 7.2.1,
rails >= 7.2.1, < 8.0.0.beta1 requires activerecord = 7.2.1 OR = 7.2.1.1 OR = 7.2.1.2 OR = 7.2.2 OR = 7.2.2.1.
Because active_record_upsert >= 0.6.1, < 0.6.3 depends on activerecord ~> 5.0.0.beta4
and active_record_upsert < 0.6.1 depends on activerecord ~> 5.0.0.beta2,
active_record_upsert < 0.6.3 requires activerecord >= 5.0.0.beta2, < 5.1.A.
And because active_record_upsert >= 0.6.3, < 0.7.0 depends on activerecord >= 5.0, < 5.1,
active_record_upsert < 0.7.0 requires activerecord >= 5.0.0.beta2, < 5.1.
And because active_record_upsert >= 0.7.0, < 0.7.3 depends on activerecord >= 5.0, < 5.2
and active_record_upsert >= 0.7.3, < 0.9.5 depends on activerecord >= 5.0, < 6.0,
active_record_upsert < 0.9.5 requires activerecord >= 5.0.0.beta2, < 6.0.
And because active_record_upsert >= 0.9.5, < 0.10.0 depends on activerecord >= 5.0, < 6.1
and active_record_upsert >= 0.10.0, < 0.11.0 depends on activerecord >= 5.0, < 6.2,
active_record_upsert < 0.11.0 requires activerecord >= 5.0.0.beta2, < 6.2.
And because active_record_upsert >= 0.11.0, < 0.11.2 depends on activerecord >= 5.2, < 7.1
and active_record_upsert >= 0.11.2 depends on activerecord >= 5.2, < 7.2,
activerecord >= 5.0.0.beta2, < 7.2 is required.
And because rails >= 7.2.1, < 8.0.0.beta1 requires activerecord = 7.2.1 OR = 7.2.1.1 OR = 7.2.1.2 OR = 7.2.2 OR = 7.2.2.1 (1),
rails >= 7.2.1, < 8.0.0.beta1 cannot be used.
So, because Gemfile depends on rails ~> 7.2.1,
version solving has failed.
Even if I explicitly specify the latest version in Gemfile, I still get a compatibility error.
gem 'active_record_upsert', '0.11.2' or gem 'active_record_upsert', '~> 0.11.2'
bundle
Fetching gem metadata from https://rubygems.org/.........
Resolving dependencies...
Could not find compatible versions
Because rails >= 7.2.2, < 7.2.2.1 depends on activerecord = 7.2.2
and rails >= 7.2.1.2, < 7.2.2 depends on activerecord = 7.2.1.2,
rails >= 7.2.1.2, < 7.2.2.1 requires activerecord = 7.2.1.2 OR = 7.2.2.
And because rails >= 7.2.1.1, < 7.2.1.2 depends on activerecord = 7.2.1.1
and rails >= 7.2.1, < 7.2.1.1 depends on activerecord = 7.2.1,
rails >= 7.2.1, < 7.2.2.1 requires activerecord = 7.2.1 OR = 7.2.1.1 OR = 7.2.1.2 OR = 7.2.2.
And because rails >= 7.2.2.1, < 8.0.0.beta1 depends on activerecord = 7.2.2.1
and active_record_upsert >= 0.11.2 depends on activerecord >= 5.2, < 7.2,
active_record_upsert >= 0.11.2 is incompatible with rails >= 7.2.1, < 8.0.0.beta1.
So, because Gemfile depends on rails ~> 7.2.1
and Gemfile depends on active_record_upsert = 0.11.2,
version solving has failed.
Maybe I'm doing something wrong?
The text was updated successfully, but these errors were encountered:
The gem does not install via Rubygems due to a compatibility error.
Steps to reproduce the error:
rails new test_app
gem 'active_record_upsert'
toGemfile
bundle
Even if I explicitly specify the latest version in Gemfile, I still get a compatibility error.
gem 'active_record_upsert', '0.11.2'
orgem 'active_record_upsert', '~> 0.11.2'
Maybe I'm doing something wrong?
The text was updated successfully, but these errors were encountered: