Capistrano version mismatch

[orenyk]

Apparently, even thought we specified version ~> 3.3.5 for Capistrano in our Gemfile, version 3.4.0 is being installed in ITS testing. I'm going to switch it to an exact version identifier at 3.4.0, update the version lock in the Capfile, and push a patch to v5.3.0. This should be addressed in a matter of hours (I'll try to test on DO to make sure it's working), given that it's just version number tweaks I'll probably just merge this immediately if it runs correctly.

P.S. I accidentally opened this issue on the Capistrano repository instead of ours... whoops! 😞

[orenyk]

Btw, the version lock is found in config/deploy.rb, not in the Capfile.

[orenyk]

On second thought, it looks like ITS is running production cap deploy without specifying bundle exec, so it's using the general system version of Capistrano (likely installed using gem install capistrano with no version specified, so the latest version), rather than the version specified by our Gemfile. I've asked them to try and add bundle exec to the deployment command, hopefully that resolves their issue and we can avoid a needless patch update. I'll get the code finished and issue a PR regardless, but I'll wait until we've heard back from them to decide whether or not we need to merge it.

[orenyk]

Hmmm, looks like we need to take it out of the development group for bundle exec to work (getting the error capistrano is not part of the bundle. Add it to Gemfile.). Investigating...

[orenyk]

Never mind, I had just ignored the development group during a previous bundle install. Everything's working fine now.

[orenyk]

So... if they can get it to work with v5.3.0, then I'll just close this and #1307 without merging. I'll add a note to the wiki about running Capistrano using bundle exec.