RubyMine 2019.2 Released: Faster Debugger, Ruby 2.7, Rails 6, and Much More

RubyMine 2019.2

RubyMine 2019.2 is now released!  Visit the What’s new page for a detailed overview of the new v2019.2, or check out the highlights below:


  • The debugger is significantly faster
  • Investigate every method or block on a line with Smart Step Into
  • Set breakpoints at blocks


Ruby 2.7

  • Support for pattern matching
  • Support for numbered block parameters

Ruby 2.7 pattern matching

Rails 6

  • Action Mailbox support
  • Enum support including the new negative scopes

Rails 6 Action Mailbox


  • Support for @overload and @yieldparam tags
  • Across-the-board improvements

YARD @yieldparam

Factory Bot

  • Rename and Safe Delete refactorings for factories, sequences, and traits
  • Added factories, sequences, and traits in the File Structure view and popup

Factory bot rename refactoring

Shell scripts

  • Full code insight for .sh and .bash files
  • Integrated linting and formatting tools
  • Run configurations

Shell scripts support

Check out the What’s new page for more about these enhancements and the other RubyMine improvements in JavaScript, Git, and database tools.

See the release notes for the full list of the closed tickets, and let us know if you face any issues.

Your RubyMine team

This entry was posted in Announcement and tagged . Bookmark the permalink.

4 Responses to RubyMine 2019.2 Released: Faster Debugger, Ruby 2.7, Rails 6, and Much More

  1. Eric says:

    This is great! I really hope to see a less usage of RAM in the next version, 2019.1.3 is currently taking 1.5G, it’d be nice lowering that to 1G <3

  2. Mikhail Varabyou says:

    Nice update! Breaking the debugger, skipping all breakpoints and crashing it with segfault really made it faster.
    Tested on 2019.2.1 RC either – still not working. Horrible!

    • Olga Kuvardina says:

      Could you please provide more details? Which Ruby version are you working with and where are breakpoints skipped? We had related issues but all of them have been fixed in 2019.2.1 RC so it’d be great if you could provide a reproduce scenario.

Leave a Reply

Your email address will not be published. Required fields are marked *