-
Notifications
You must be signed in to change notification settings - Fork 212
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
Upgrade bundler #3128
Comments
It looks like this is because of Heroku config - on staging we were still on heroku-18, and trying to upgrade to heroku-20, which also has old bundler. Upgrading to heroku-22 in progress to see if that helps. |
Okay, apparently Heroku looks not just at the bundled-with, but also the other bits of the gemfile.lock, so we need to update those as well before it will deploy with the right bundler. https://devcenter.heroku.com/articles/ruby-support#libraries |
In heroku, I cancelled the upgrade to -22 for the moment. Will muck around with various deps shortly |
Hmm, looks like this was already fixed in dev. |
... facepalm WHY. |
6e21cae + version-18 fixed the bundler problem. |
|
Deploy is now failing because apparently our Gemfile needs bundler 2 or later, and we're on 1.x. I don't currently have a working dev env, can someone do the honours of uplifting everything?
The text was updated successfully, but these errors were encountered: