Cannot published gem using "rake release"

[roback]

Since we started using 2FA for RubyGems we can't publish gems using bundle exec rake release. Rake gets stuck on the release:rubygem_push task, as shown when running with --trace:

$ bundle exec rake release --trace
** Invoke release (first_time)
** Invoke build (first_time)
** Execute build
capistrano-twingly 4.0.0 built to pkg/capistrano-twingly-4.0.0.gem.
** Invoke release:guard_clean (first_time)
** Execute release:guard_clean
** Invoke release:source_control_push (first_time)
** Execute release:source_control_push
Tag v4.0.0 has already been created.
** Invoke release:rubygem_push (first_time)
** Execute release:rubygem_push

Running gem push manually shows exactly what's happening:

$ gem push pkg/capistrano-twingly-4.0.0.gem
Pushing gem to https://rubygems.org...
You have enabled multi-factor authentication. Please enter OTP code.
Code:

After entering the 2FA/OTP code, the gem gets published successfully.

[dentarg]

Here's the upstream issue for this: rubygems/bundler#6854

[dentarg]

Here's the upstream issue for this: bundler/bundler#6854

And they have two outstanding PRs for it:

• Allow OTP code to be passed through bundler rubygems/bundler#7005 by contributor
• Fix GemHelper to allow reading Input/Output rubygems/bundler#7108 the PR above but changed by bundler team member, seems like they are thinking about how to best add tests for it now

[dentarg]

Progress is being made, rubygems/bundler#6854 was closed upstream by rubygems/bundler#7199 :)

[dentarg]

Looks like the fix will be in Bundler v2.1 (twingly/twingly-url#139 (comment)). I've also changed our Rubygems settings to not require OTP code on gem push.