3.1.13 May 31 2019

• No longer include compiled binaries for Windows. See GH #173.
• Update C and Java implementations to latest versions [GH #182 by @fonica]
• Bump default cost to 12 [GH #181 by @bdewater]
• Remove explicit support for Rubies 1.8 and 1.9
• Start calibration from the minimum cost supported by the algorithm [GH #206 by @sergey-alekseev]
• Remove explicit support for Rubies 1.8 and 1.9 [GH #185 by @tjschuck]
• Define SKIP_GNU token when building extension (Fixes FreeBSD >= 12) [GH #189 by @adam12]

• Add support for Ruby 2.3, 2.4, and 2.5 in compiled Windows binaries
• Fix compatibility with libxcrypt [GH #164 by @besser82]

• Add support for Ruby 2.3, 2.4, and 2.5 in compiled Windows binaries
• Fix compatibility with libxcrypt [GH #164 by @besser82]

• Add support for Ruby 2.2 in compiled Windows binaries

• Fix issue with dumping a BCrypt::Password instance to YAML in Ruby 2.2 [GH #107 by @mattwildig]

• Rebuild corrupt binaries

• Add support for Ruby 2.1 in compiled Windows binaries [GH #102]

• Rebuild corrupt Java binary version of gem [GH #90]
• The 2.1 support for Windows binaries alleged in 3.1.3 was a lie -- documentation removed

Version 3.1.6 on RubyGems

Release Notes

• Nothing! The dummy version of the old "bcrypt-ruby" named gem needed a couple version bumps to fix some bugs. It felt wrong to have that at a higher version than the real gem, so the real gem is getting bumped to 3.1.6.

Version 3.1.3 on RubyGems

Release Notes

• Add support for Ruby 2.1 in compiled Windows binaries
• Rename gem from "bcrypt-ruby" to just "bcrypt": #86