bootboot
bootboot copied to clipboard
Dualboot your Ruby app made easy
We have the following in our `Gemfile`: ``` ruby ">= 2.7.0", "< 3.1" ``` When running with bootboot on ruby 2.7.6, we get the following error: ``` Could not find...
I haven't figured it out yet and if someone has, here may be a reasonable place for it to exist.. how someone might manage or configure a `.github/dependabot.yml` to handle...
Hello, and thank you for this Bundler plugin. I am trying to deploy a review app to Heroku with this plugin. It seems to install perfectly fine: ``` -----> Ruby...
While experimenting with this plugin I ran into a couple of cases that felt a bit unintuitive: - Suppose we had an already-existing barebones setup (i.e. Gemfile_next.lock is present) and...
When running `bundle update xxx --conservative` bootboot should only update the xxx dependency in the Gemfile_next.lock, not subdependencies of xxx
If the Gemfile.lock got updated by someone running `bundle lock --update my_gem`, bootboot isn't able to update the Gemfile_next.lock because the Bundler `after-install-all` hook is not triggered by Bundler. Second...
When writing the Gemfile_next.lock snapshot, we resolve the dependencies remotely https://github.com/Shopify/bootboot/blob/master/lib/bootboot/gemfile_next_auto_sync.rb#L56 this is unnecessary as all the gems should already have been fetched. Resolving the dependencies locally with `Bundler::Definition#resolve_with_cache` https://github.com/bundler/bundler/blob/a63a39d738865665f714f179fe42dd10006da26d/lib/bundler/definition.rb#L148...
Hello, We recently were trying to update from Bundler v2.2.32 to v2.3.22 and ran into the following error: ``` NoMethodError: undefined method `to_gem_version_with_patchlevel' for # /.bundle/plugin/gems/bootboot-0.2.0/lib/bootboot/ruby_source.rb:29:in `block in specs' /.rbenv/versions/2.7.3/lib/ruby/gems/2.7.0/gems/bundler-2.3.22/lib/bundler/index.rb:9:in...
After installing BootBoot, when I run `bundle update` (regardless of whether or not I have `DEPENDENCIES_NEXT` environment variable set), only the `Gemfile_next.lock` is being updated, `Gemfile.lock` is unchanged. This is...
I checked if it passes all tests. There was an issue, but I fixed it upstream though https://github.com/rubygems/rubygems/pull/7066.