Capistrano version conflict about wp-deploy

[royemmerich]

I have now discovered that if I change the Capistrano version in config/deploy.rb from 3.1.0 to 3.2.1 and leave the version in Gemfile.lock as 3.1.0 you end up getting the following error message when running a Capistrano command:

cap aborted!
Capfile locked at 3.2.1, but 3.1.0 is loaded

I then thought I was going to be clever and change the version number in Gemfile.lock to

  specs:
    capistrano (>= 3.1.0)

but this just returns the following error when running a Capistrano command:

Malformed version number string >= 3.1.0 (ArgumentError)

So instead my Gemfile.lock file now looks like this:

  specs:
    capistrano (3.2.1)

[aaronthomas]

First off, you should always make sure you use bundle exec when you're running Capistrano commands to ensure you're executing the bundled version (3.1.0) rather than the global version you have installed on your machine (presumably 3.2.1).

The reason we've locked the config (and bundle) at 3.1.0 is to avoid compatibility issues with future versions of Capistrano.

You should never directly edit your Gemfile.lock – that will be why you're getting the malformed version string error. Instead, you should the Gemfile then run bundle update capistrano which will update the lock file for you. However, I wouldn't recommend updating the bundle as I can't ensure wp-deploy will work with all future versions of Capistrano.

[royemmerich]

As you have probably realised, I have/had zero experience with Ruby until I started working with Capistrano.

All of the confusion in this issue prompted me to do a bit of research. I found the following page very helpful in explaining the rationale behind the Gemfile

[aaronthomas]

Likewise, I'm also not a Ruby developer – my experience is limited to the work I do with this framework and a couple of other minor closed-source projects. The README for this assumes a basic understanding of Bundler and Gemfiles, but perhaps I should clarify that a little more in the documentation.