The BootBoot gem makes it very easy to run tests against against future versions of Rails.
When running bundle install it produces a Gemfile_next.lock alongside the usual Gemfile.lock. At the moment Dependabot only checks in the Gemfile.lock and I guess it ignores the Gemfile_next.lock as this is a non-standard file. The result is an error is raised when the CI attempts run bundler before running the tests.
Here's an example of the error output:
Using bundler 2.0.2
Installed plugin bootboot
You are trying to install in deployment mode after changing
your Gemfile. Run `bundle install` elsewhere and add the
updated Gemfile_next.lock to version control.
The dependencies in your gemfile changed
You have added to the Gemfile:
* activeadmin (~> 2.3.1)
You have deleted from the Gemfile:
* activeadmin (~> 2.2.0)
The command "eval bundle install --jobs=3 --retry=3 --deployment --path=${BUNDLE_PATH:-vendor/bundle} " failed.
It would be great if there was some way to specify any custom lock files (or maybe just any non-standard output) that should be committed by Dependabot. Does this sound like a sane idea?
The BootBoot gem makes it very easy to run tests against against future versions of Rails.
When running
bundle installit produces aGemfile_next.lockalongside the usualGemfile.lock. At the moment Dependabot only checks in theGemfile.lockand I guess it ignores theGemfile_next.lockas this is a non-standard file. The result is an error is raised when the CI attempts run bundler before running the tests.Here's an example of the error output:
It would be great if there was some way to specify any custom lock files (or maybe just any non-standard output) that should be committed by Dependabot. Does this sound like a sane idea?