-
Notifications
You must be signed in to change notification settings - Fork 45
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
New rubygems release? #80
Comments
@brchristian thanks for noticing, we'll work on a new release on Friday! |
@brchristian I think it makes sense for #79 to be fixed, what do you think? |
@aldesantis I'm not sure what's going on to cause #79! We are running the current github |
@brchristian I'll take a look to understand if it's an issue with the gem or the Solidus install so that we know we're not releasing a broken gem. 🙂 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I notice that the last rubygems release of this extension was from 2016, and a lot has changed in the world of Solidus since then.
In fact, I cannot even install the most recent rubygems version!
If I create a brand new Ruby (2.6.6), Rails (5.1.7), Solidus (2.10.2), and solidus_related_products (1.1.0) application, I can’t run the migrations, as I get:
I suspect this can be fixed by simply cutting a newer version of the gem!
The text was updated successfully, but these errors were encountered: