Install the latest bundler version: gem install bundler Fetching bundler-2.3.5.gem Successfully installed bundler-2.3.5 1 gem installed Update the bundler version in Gemfile.lock: bundle update --bundler Confirm it worked:
...specified under BUNDLED_WITH in the Gemfile.lock. This had two annoying consequences: If the bundler version on your system was lower than in the Gemfile.lock, you got an error message...
...and had to manually install the correct version. If the bundler version on your system was higher than in the Gemfile.lock, bundler silently updated the version in the Gemfile.lock to...
Some rubygems come in platform-specific versions (i.e. "x86_64-linux") in addition to the usual "ruby" platform. This is...
Calling bundle update GEMNAME will update a lot more gems than you think. E.g. when you do this...
...ruby-version: ".ruby-version" bundler-cache: true cache-version: 1 - name: Verify Ruby and Bundler versions run: | ruby -v bundle -v shell: bash - name: Test postgres connection run: "psql $DATABASE...
makandra is responsible for maintaining about 75 Ruby projects. These projects use a large number of different versions for Ruby...
...will take care of a few things: The new Ruby version is installed The Bundler version stated in the Gemfile.lock is installed Geordi is installed (for database dumps)
Ruby includes many standard gems that are bundled into the Ruby installation. Here is an example for the gem strscan...
The linked GitHub repository is a bit like our "dev" cards deck, but groomed from a single person (Josh Branchaud...
...version of bundler, but don't want to uninstall newer ones): bundle _1.0.10_ -v Bundler version 1.0.10 An example is rails 3.2, which freezes bundler at version ~> 1.0:
...In Gemfile: rails (~> 3.2) was resolved to 3.2.0, which depends on bundler (~> 1.0) Current Bundler version: bundler (1.13.6) You can solve this with: gem install bundler -v 1.0.10
So you're getting this failure when running bundle install on an older project: Your Gemfile.lock is corrupt. The following...
When installing a gem you can use version comparators like >= or ~>. That way it is possible to fetch the latest...
tl;dr: Ruby's Bundler environment is passed on to system calls, which may not be what you may want...
It most cases it's not necessary to add a version constraint next to your gems in the Gemfile. Since...
You need to update a lof gems. Make sure you don't have any version constraints in your...
Web security basics Einführung in die Web Security 🇩🇪 provides essentials for the topic of this card. Read following chapters:
Bundler 2 requires at least Ruby 2.3.0 and RubyGems 2.5.0. You might get the following error when you try to...
...LOADED_SPECS_MUTEX (NameError). Given the following project: ruby -v ruby 1.8.7 bundler -v Bundler version 1.13.7 gem -v 1.8.30 rails -v Rails 3.2.22.1 Running specs or features resulted in...
...seems not to work here, so I used (also described in the card) a bundler version > 1.15 (exactly 1.16.1). This fixed the issue...
Just like we use gems on the server, we use third party JavaScript libraries in the browser. These typically provide...
When a Ruby version gem has a letter in its version number, it is considered a pre-release:
So you're getting an error like this: undefined method `activate_bin_path' for Gem:Module (NoMethodError)
While deploying an Ruby update to an old application these days, we encountered the following misleading error: *** [err :: some-host.makandra.de] You...
When upgrading Rails versions -- especially major versions -- you will run into a lot of unique issues, depending on the exact...
Using Ruby 1.8.7 you will not be able to use the maximum versions Rubygems 1.8.30 and Bundler 1.17.3 with https://...