2.3.3 (Dec 07, 2016)

Ruby 2.3.3

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.3.X is brand new

While officially 2.3 is stable, that doesn't mean all the software will magically work on it.

Use 2.3 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.# compatible

Ruby 2.3 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.3.

DO NOT install Ruby 2.3 on top of existing Ruby 2.2.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

388524ce450123c25e2d799f6a670b96 *ruby-2.3.3-doc-chm.7z
0baf1559473512468d150df14a20a37a *ruby-2.3.3-i386-mingw32.7z
7ec844390d2e66cfa5fa5a6d1cebc80a *ruby-2.3.3-x64-mingw32.7z
b2688631f3eac70dc45a1735ba8ef748 *rubyinstaller-2.3.3-x64.exe
0447f419345bcad7e34dbca8d42b09d0 *rubyinstaller-2.3.3.exe

SHA256:

6e011a18ffa34b40301be3c2dfffa81df3012e98e0e93575052b8d5314f45ebe *ruby-2.3.3-doc-chm.7z
5022ef928f0296abede90f1cf4346250d69f6298c648cad6279938f64eca29fa *ruby-2.3.3-i386-mingw32.7z
92b97ac3eb380f3f1b7b655a328668cf02b2846ad3c20135bd51f45f4c1cbfc8 *ruby-2.3.3-x64-mingw32.7z
3d0a4ad06c5503e1cb88827443593969e689ac96b5161140b08f0becb7b792cf *rubyinstaller-2.3.3-x64.exe
43110f9bcd8a067d69409507cad6a43f1fcf05e8bd64d096dd9df47475de50f3 *rubyinstaller-2.3.3.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.3 to 2.3.3
  • Upgraded OpenSSL to 1.0.2j
  • Upgraded libffi to 3.2.1
  • Upgraded LibYAML to 0.1.7
  • Upgraded tcl & tk to 8.5.19
2.2.6 (Dec 07, 2016)

Ruby 2.2.6

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.2.x is stable

While officially 2.2.x is stable, that doesn't mean all the software will magically work on it.

Use 2.2 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.2 compatible

Ruby 2.2 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.2.

DO NOT install Ruby 2.2 on top of existing Ruby 2.1.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

14b16d6f2886986db02588f7cd0278aa *ruby-2.2.6-doc-chm.7z
c6cf3609069c0735b0d5f0476ced8ca8 *ruby-2.2.6-i386-mingw32.7z
2b8736d65bf94e3dd49e36dc3b41d4e7 *ruby-2.2.6-x64-mingw32.7z
f07804aba4cc67215a71befb33b1cd9e *rubyinstaller-2.2.6-x64.exe
74cebff54665d9c80c081c060f03c657 *rubyinstaller-2.2.6.exe

SHA256:

abccdb0fc70dc187391aba1fb59869523eee68f3b752f53775f8a481c3481812 *ruby-2.2.6-doc-chm.7z
cc9a104fb74ec45523b0e40ac66225ec8a3e66b2a6fc0c46f1adc691cb14e3cb *ruby-2.2.6-i386-mingw32.7z
b9d904209277f0ae005890046053d67fd7841635a4f507c1e8d88f1d25a37586 *ruby-2.2.6-x64-mingw32.7z
d1205b461f15f9dc6ad1eac08bf5a77dd2bce3a37095e5f09ac6e45bc334c198 *rubyinstaller-2.2.6-x64.exe
b53bb768aea3946178149a804201e68ddc034ba5140f2488c2520da24f76e3cc *rubyinstaller-2.2.6.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.2 to 2.2.6
  • Upgraded OpenSSL to 1.0.2j
  • Upgraded libffi to 3.2.1
  • Upgraded LibYAML to 0.1.7
  • Upgraded tcl & tk to 8.5.19
2.2.5 (Jul 17, 2016)

Ruby 2.2.5

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.2.x is brand new

While officially 2.2.x is stable, that doesn't mean all the software will magically work on it.

Use 2.2 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.2 compatible

Ruby 2.2 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.2.

DO NOT install Ruby 2.2 on top of existing Ruby 2.1.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails to detect x64 installations of Ruby. You will need to manually edit config.yml for it to work. See the following issues for details:

MD5:

eb72301948a7d46a6bcf1d79bed20880 *ruby-2.2.5-doc-chm.7z
c9209bd9fe7a3b2e593b00592ce6a94d *ruby-2.2.5-i386-mingw32.7z
cb1c2e9a6e5eb3d5a9893f5a811d1d0b *ruby-2.2.5-x64-mingw32.7z
98ba0dba225e731fc50b983bb52d9dd8 *rubyinstaller-2.2.5-x64.exe
b4bf6354a8e0b3f181c9a1cb890bada0 *rubyinstaller-2.2.5.exe

SHA256:

04cbdcc6681eaf476739681d608b0b4b2544e0c41fc0b367f648fa5816f766d9 *ruby-2.2.5-doc-chm.7z
be0dd3f56986ffaf4789a9978ca6d155abf5407db2a64e8abd82c61035bfb274 *ruby-2.2.5-i386-mingw32.7z
517e9bf81cac48d4ba3212e1950d542c4ac2106fc7f0af49160eadcfa0d66d16 *ruby-2.2.5-x64-mingw32.7z
43fff3fccbcf42d0d3fbe7bd84d37416bf844b8e5b56e357af60e0519c002732 *rubyinstaller-2.2.5-x64.exe
063d80ee6766d6e691cd94d6572c0cb0533e325e19ec2dccb787d29bfdce41a8 *rubyinstaller-2.2.5.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.2 to 2.2.5
2.1.9 (Jul 17, 2016)

Ruby 2.1.9

Packages will be provided in two versions: 32bits (x86) and 64bits (x64).

The DevKit used for version the Ruby 2.0 series is required for this version.

Last Normal Release

This is the last normal release for the Ruby 2.1 series.

From the official release page:

As announced before, this is the last normal release of the Ruby 2.1 series. After this release we will never backport any bug fixes to 2.1 except security fixes. We recommend that you start planning to upgrade to Ruby 2.3 or 2.2.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.1 compatible

Ruby 2.1 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 2.0.0 or 2.2, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails to detect x64 installations of Ruby. You will need to manually edit config.yml for it to work. See the following issues for details:

MD5:

b34dbbc990ed5d2dbfff8aec8ce136bf *ruby-2.1.9-doc-chm.7z
96cd91e13debca9841dc8762b7ffa888 *ruby-2.1.9-i386-mingw32.7z
97cf13ef1e0eddeb31941696ab5a4042 *ruby-2.1.9-x64-mingw32.7z
030caa80bd9aca042d8382a7de33d791 *rubyinstaller-2.1.9-x64.exe
d54287f6f0de31091bdf07073ee81f2d *rubyinstaller-2.1.9.exe

SHA256:

165032fb247b57f27095b643fc1bd7fa29de71381dc1172a00952a8e80ff55b0 *ruby-2.1.9-doc-chm.7z
f8a28e27ebd502a10b8683377bd71dcc1b49b5269cee25698e11cfe0395640dd *ruby-2.1.9-i386-mingw32.7z
abc6f5335d7676598ea9bb7fe70ed9845e68720dde987264eae0bc6ea037c726 *ruby-2.1.9-x64-mingw32.7z
aadd8fe9ff1ea2cda58019a3c48c83206e8016e265c19d746493ad26edd89987 *rubyinstaller-2.1.9-x64.exe
946101ebbe729f1a26f9836ac7485a7449a0ea3c7325c973ff2a3548edc2e488 *rubyinstaller-2.1.9.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.9
2.3.1 (Jul 17, 2016)

Ruby 2.3.1

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.3.X is brand new

While officially 2.3 is stable, that doesn't mean all the software will magically work on it.

Use 2.3 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.# compatible

Ruby 2.3 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.3.

DO NOT install Ruby 2.3 on top of existing Ruby 2.2.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

4cd318575c2e2a5ea85d8bb0cda0761d *ruby-2.3.1-doc-chm.7z
1fe8c2e6e6dfc0ecaaa40c30336dcf03 *ruby-2.3.1-i386-mingw32.7z
e0e57f9db6b594770985434a0aa03866 *ruby-2.3.1-x64-mingw32.7z
7e983ed41df0dbdb701fa140cbb2fed0 *rubyinstaller-2.3.1-x64.exe
a54cd84886b207def954a3a834d36f4b *rubyinstaller-2.3.1.exe

SHA256:

be51692457777db238b3ac5c34e09e887574c268d67cba266ed9aa08486529e9 *ruby-2.3.1-doc-chm.7z
24eddf097265dd8010e1118ef88428de0d182adfec6a6adb8073ca3dfcdec321 *ruby-2.3.1-i386-mingw32.7z
d033e0343147d178a04752dbd0758311967189d37c16e9329828606b5a87be7d *ruby-2.3.1-x64-mingw32.7z
a883e24b9a2b383170e17c372cec32bdeb2804ebc1ca5997d68d97cdddae883c *rubyinstaller-2.3.1-x64.exe
5883233e5477c8097e68ec4bb47932011664d8d3a46595a9440bfd47c9dc78cb *rubyinstaller-2.3.1.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.3 to 2.3.1
2.3.0 (Apr 05, 2016)

Ruby 2.3.0

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.3.0 is brand new

While officially 2.3 is stable, that doesn't mean all the software will magically work on it.

Use 2.3 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.# compatible

Ruby 2.3 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.3.

DO NOT install Ruby 2.3 on top of existing Ruby 2.2.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

282471c130ded24a368049d3a5ac5c63 *ruby-2.3.0-doc-chm.7z
95a62cb2ba42f80d9f5a36df07d5886a *ruby-2.3.0-i386-mingw32.7z
1d63ef1fbc06078c43b596326c4144a0 *ruby-2.3.0-x64-mingw32.7z
d9e18b23821e998cb9bd230495092ddd *rubyinstaller-2.3.0-x64.exe
3a2ff624ace7bee995bead28dc49b216 *rubyinstaller-2.3.0.exe

SHA256

17bcd8fb55c10effc3ae73eed58ab3d492d2bb0362e394d5bfc34e57074d944e *ruby-2.3.0-doc-chm.7z
c8daba86954ddb59a8ff3b1bb5dbb24fb0c4c06810d9067fabac870b9316b029 *ruby-2.3.0-i386-mingw32.7z
e930827ecd075b7fc9cca50df2824c6b8fba26f90e92eae2e41d58edf74dbfc9 *ruby-2.3.0-x64-mingw32.7z
087a7e3404fc2892f7eae6e8d0a12de419d57a8a4d78bbcf95568cb75f086a99 *rubyinstaller-2.3.0-x64.exe
f7926dd87bc2f436ea1f407073a01ace38285818578a8764e2c1ec93aaead3c6 *rubyinstaller-2.3.0.exe

Official Announcement:

Enhancements:

  • Added Ruby 2.3.0 to recipes
2.2.4 (Feb 04, 2016)

Ruby 2.2.4

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.2 compatible

Ruby 2.2 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.2.

DO NOT install Ruby 2.2 on top of existing Ruby 2.1.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

902eca58427b9fba4d212b68611e0a88 *ruby-2.2.4-doc-chm.7z
392a3d4ebc8d0733508c8e70ec86d0fa *ruby-2.2.4-i386-mingw32.7z
0cff85bfccdd6a1e772cdf362066199e *ruby-2.2.4-x64-mingw32.7z
10cb6661bf26cbd2f1c0cbd32a830856 *rubyinstaller-2.2.4-x64.exe
c46e25c2fd3a68fa7a14713cd09eb050 *rubyinstaller-2.2.4.exe

SHA256

b32399c9e8367d470697fc24e1a677e9af4bd9bc761d60cce22133621f1495d7 *ruby-2.2.4-doc-chm.7z
da8a3ec5ac4ac23f21037e5132ea1362d56c8846bcba2209a4125928f88a8015 *ruby-2.2.4-i386-mingw32.7z
9e8c1eea5b7fd732efd3207210c17b7d0620858f33966652f0bb2566fe04c660 *ruby-2.2.4-x64-mingw32.7z
f600c3d1baff0dcf5fd86280e6e9c4703ceb9c641a7fef90fb551c8c6f5825fd *rubyinstaller-2.2.4-x64.exe
eb367eb63a15d9b594be97015da12cf3ef608a5abca125d0a24f537a8bf1f8ef *rubyinstaller-2.2.4.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.2 to 2.2.4
2.1.8 (Feb 04, 2016)

Ruby 2.1.8

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

The DevKit used for version the Ruby 2.0 series is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important
you understand that not all gems, libraries or tools have been tested
for this version.

Things are pretty close, however it is still our recommendation you
use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as
there is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.1 compatible

Ruby 2.1 introduced some C API changes which means compiled C
extensions with previous versions of Ruby may not run against Ruby
2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 2.0.0 or 2.2, or
try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for
that gem to compile. Look at the gem documentation for the
requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result
in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name
'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits
respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

bfd67e83ef42bc93baf107a14856807e *ruby-2.1.8-doc-chm.7z
8c2ff85d3318c2cfdaeb4f64f5bf4159 *ruby-2.1.8-i386-mingw32.7z
bbf553451fd1f5524c132517201902df *ruby-2.1.8-x64-mingw32.7z
102414fa52fae14628ea10a179a9c22a *rubyinstaller-2.1.8-x64.exe
086b160f845af6042565d5213243f127 *rubyinstaller-2.1.8.exe

SHA256

9a7462a37a7e1f7bfeef40c5966e54059143f74c958b8f47a2c8f7f5f052ca08 *ruby-2.1.8-doc-chm.7z
1776677436f5c57bcf0a74ccb77ca8e08c28acecb85cf7f851edb17a721ba3d8 *ruby-2.1.8-i386-mingw32.7z
92910f50002906d48de1a86e104d61be3766a7195ab99d71af41e00115e99fda *ruby-2.1.8-x64-mingw32.7z
e991390a89af7e4736db991a2b759bb826de8be39218305797fc879923ea964a *rubyinstaller-2.1.8-x64.exe
eee3c6be5da51afd69e258c911ccd6bd27091766dad1fba0e7420d4d1a8e1ad8 *rubyinstaller-2.1.8.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.8
2.0.0-p648 (Feb 04, 2016)

Ruby 2.0.0-p648

This is a Security Maintenance Relase

Ruby 2.0.0 has gone into the state of the security maintenance phase.
This means there will be no more releases in the 2.0.0 series unless any
critical regressions or security issues are found.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

Things are pretty close, however it is still our recommendation you
use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 and 2.1 introduced ABI breakage which means compiled C extensions from
releases in the 1.9.3 or 2.1.X series will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3 or 2.1.X, or
try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

24e5eca760a487c87add7dc06cb18832 *ruby-2.0.0-p648-doc-chm.7z
36de40a85256396280592b249e0ccb3d *ruby-2.0.0-p648-i386-mingw32.7z
022f14d020eb2b7a19c6494f7e16d137 *ruby-2.0.0-p648-x64-mingw32.7z
348527ed847466e28d56cfe2e8f73e7c *rubyinstaller-2.0.0-p648-x64.exe
790cab5bdbe838da28036494545600b8 *rubyinstaller-2.0.0-p648.exe

SHA256:

42e37920515318c371ec53b5b43e1b11e979d6f5773fa42b1b69233a6aec4edf *ruby-2.0.0-p648-doc-chm.7z
0a9c61ba46e37d36cb5efdc5957af1ec352729ec75d3aa5c020d1581a67ee636 *ruby-2.0.0-p648-i386-mingw32.7z
094990f48608853f6d3a02d9937db29afc9603c9b34b8258152efd63a70976df *ruby-2.0.0-p648-x64-mingw32.7z
c38f6fa702383fb683ab7a95ab1fff3db521a33a5c6cbcbba8ae7618e821ec17 *rubyinstaller-2.0.0-p648-x64.exe
f4c7b92ee0e43d59ed3cf4e1122e13526b1b3af38ae7f39b1a61d8e99ecaace0 *rubyinstaller-2.0.0-p648.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 648
2.1.7 (Sep 03, 2015)

Ruby 2.1.7

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

The DevKit used for version the Ruby 2.0 series is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important
you understand that not all gems, libraries or tools have been tested
for this version.

Things are pretty close, however it is still our recommendation you
use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as
there is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.1 compatible

Ruby 2.1 introduced some C API changes which means compiled C
extensions with previous versions of Ruby may not run against Ruby
2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 2.0.0 or 2.2, or
try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for
that gem to compile. Look at the gem documentation for the
requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result
in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name
'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits
respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

49ec022e2b127dc20f7b7011d1dbc378 *ruby-2.1.7-doc-chm.7z
ed0af70cb991bc30a4a78f39e02f39de *ruby-2.1.7-i386-mingw32.7z
6f77454f8c3935f0113707b8f65faf14 *ruby-2.1.7-x64-mingw32.7z
56751f595ecc5385008967c5c582027e *rubyinstaller-2.1.7-x64.exe
57efcc7ea3e031e66e2951db85ed09fe *rubyinstaller-2.1.7.exe

SHA256

2f7e36bc059a77dba5157de08306e24fc0fd7e0517f490231e61df5f7496da92 *ruby-2.1.7-doc-chm.7z
cf6e9f4bb156e70df4dcb5052011296edeb16bf02a4a4e476899a03ceed9a248 *ruby-2.1.7-i386-mingw32.7z
711ca6c510adb921ed1db66a01963767040dfbdec65949ef616279c76dba7e9e *ruby-2.1.7-x64-mingw32.7z
b60791aa333c5a540f41647e2c82256d77f75481843d30d098cb1481a51447e7 *rubyinstaller-2.1.7-x64.exe
c7c805c8310919d6deed1b1b6ef7ddc6c0c83b0a79e8521876ecb156da020684 *rubyinstaller-2.1.7.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.7
2.0.0-p647 (Sep 03, 2015)

Ruby 2.0.0-p647

This is a Security Maintenance Relase

Ruby 2.0.0 has gone into the state of the security maintenance phase.
This means there will be no more releases in the 2.0.0 series unless any
critical regressions or security issues are found.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

Things are pretty close, however it is still our recommendation you
use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 and 2.1 introduced ABI breakage which means compiled C extensions from
releases in the 1.9.3 or 2.1.X series will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3 or 2.1.X, or
try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

ae5e221b7796c76e7e89287908bb90f5 *ruby-2.0.0-p647-doc-chm.7z
a65e229c275993898e72cea690a5db1b *ruby-2.0.0-p647-i386-mingw32.7z
d641e1a26e17d15d0419c7e3830e5683 *ruby-2.0.0-p647-x64-mingw32.7z
ad79743badb81f7d6c9fcd5cb8c5b809 *rubyinstaller-2.0.0-p647-x64.exe
c09e99c250681f6fa7ec592267dcc76f *rubyinstaller-2.0.0-p647.exe

SHA256:

418dc7881cdad117efed30953859d89ece8cce77ae4f7ac587e6ab7845287ef3 *ruby-2.0.0-p647-doc-chm.7z
b5f8ff6c8cd71078bbbce1bffdac92e3189c54d1982eb4b4d4a4c3417c3fce60 *ruby-2.0.0-p647-i386-mingw32.7z
004878473f10e5cc22452f8594cd272d913e7fcb2e0275242555de41524615c8 *ruby-2.0.0-p647-x64-mingw32.7z
0adf68a5ef96789b529cd53a3888db06c540929954b2135bc235f56591fe978d *rubyinstaller-2.0.0-p647-x64.exe
bb3a0cc3bc19b3f9731801f52d1c3400148a7b9f308e6d82219bd69257329630 *rubyinstaller-2.0.0-p647.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 647
2.2.3 (Sep 03, 2015)

Ruby 2.2.3

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.2.x is brand new

While officially 2.2.x is stable, that doesn't mean all the software will magically work on it.

Use 2.2.3 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.2 compatible

Ruby 2.2 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.2.

DO NOT install Ruby 2.2 on top of existing Ruby 2.1.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

8a31941c8907fef7f31e888b3c78ac10 *ruby-2.2.3-doc-chm.7z
8d7d94856bd7c9498c48a9b8d155c926 *ruby-2.2.3-i386-mingw32.7z
77bfcf4b65ec8d5ba0cd84779f3eff7c *ruby-2.2.3-x64-mingw32.7z
9f123f08f1045ad1d49a99031f3e835e *rubyinstaller-2.2.3-x64.exe
2da40c04d7a3906b269e739b5627304f *rubyinstaller-2.2.3.exe

SHA256

b106e05a247b2665f9c0cdb9ea195153756101d5b8553a31816668644efe0357 *ruby-2.2.3-doc-chm.7z
08b33a85ec26c01a6d305a258680976b57081e22ad9196623c1cf154e558e3ce *ruby-2.2.3-i386-mingw32.7z
683270a7e09ef756476c00902eda9999137468eb21a371831b7c01602d2fd069 *ruby-2.2.3-x64-mingw32.7z
ca4dadefce6a5adbd4bdd1d960edc0d99d4e05af749e1ed7678476540b7443db *rubyinstaller-2.2.3-x64.exe
e651c9a7abcc120b5703d9024942b121460084595489dc6f2306a71127cd901e *rubyinstaller-2.2.3.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.2 to 2.2.3
2.2.2 (Apr 16, 2015)

Ruby 2.2.2

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

The DevKit used for version the Ruby 2.0 series is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.2.x is brand new

While officially 2.2.x is stable, that doesn't mean all the software will magically work on it.

There were breaking bugs in 2.2.1 which didn't allow gems to be cross-compiled.
So many gems will not yet have fat binaries for Ruby 2.2.2. This situation is expected to get better soon.

Use 2.2.2 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.2 compatible

Ruby 2.2 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.2.

DO NOT install Ruby 2.2 on top of existing Ruby 2.1.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

69ac5e5e9d687c35989393bf6e7b15f9 *ruby-2.2.2-doc-chm.7z
ee0d7604eb267dd086a0401c4314d5f7 *ruby-2.2.2-i386-mingw32.7z
f36b211f97a2421154667d7af6f0ef40 *ruby-2.2.2-x64-mingw32.7z
bd8675404063cf814e38579fd53ac39f *rubyinstaller-2.2.2-x64.exe
b730da8dda79107681f88423c2b6926d *rubyinstaller-2.2.2.exe

SHA256

82866bd5881ec48b0e83cc37ac5ff374b044aff977c38de3a190151f9d31a476 *ruby-2.2.2-doc-chm.7z
5831bb35208cd0004a25675863d04a9da89ffa53d0f393cbbb794776b33d43bd *ruby-2.2.2-i386-mingw32.7z
5db1f9af028fd5e60e5056b2bac85ca6f46d7755eb56a9c04b1dd854947b417c *ruby-2.2.2-x64-mingw32.7z
25cbd5cb02d4c1b73d8386ee123c68d61aafa6c879fc6230a51016278fae3950 *rubyinstaller-2.2.2-x64.exe
53c04fd0d60a640ae868ff917b284da7c0131be8242d7953b69829a011abfd5c *rubyinstaller-2.2.2.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.2 to 2.2.2
2.1.6 (Apr 16, 2015)

Ruby 2.1.6

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

The DevKit used for version the Ruby 2.0 series is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.1 compatible

Ruby 2.1 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 2.0.0 or 2.2, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

55aba3c8acad440757fdead17493c148 *ruby-2.1.6-doc-chm.7z
e3c345a73e5523677a1f301caa4142eb *ruby-2.1.6-i386-mingw32.7z
a443794bc4c22091193eccf0b02f763e *ruby-2.1.6-x64-mingw32.7z
50a2c0097532a4086fa58b6507f6181c *rubyinstaller-2.1.6-x64.exe
03ff673c610d17e2ab41e7fa7e020758 *rubyinstaller-2.1.6.exe

SHA256

0f8137ef7c4f24653f2e93159822542195b0c9a780dbddd4bf2398e7815cf611 *ruby-2.1.6-doc-chm.7z
7c8ce382002892602d908a516777abd5fb9bc630574382a4cf64b205b8380e8b *ruby-2.1.6-i386-mingw32.7z
c2de5f535df2c52d53bacde207103db707e61678f0421c3ecbbf6dff510f8ed8 *ruby-2.1.6-x64-mingw32.7z
f99edeaa2f192403536ec13070d9bf5936a634f8396ed896757129260169c853 *rubyinstaller-2.1.6-x64.exe
c31861c252031928c661b58accfc9b02fbd63d35d03844b08811ae8094cc401e *rubyinstaller-2.1.6.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.6
  • Updated Readme to markdown format
  • Upgraded OpenSSL to version 1.0.1l
2.0.0-p645 (Apr 16, 2015)

Ruby 2.0.0-p645

This is a Security Maintenance Relase

Ruby 2.0.0 has gone into the state of the security maintenance phase.
This means there will be no more releases in the 2.0.0 series unless any
critical regressions or security issues are found.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 and 2.1 introduced ABI breakage which means compiled C extensions from
releases in the 1.9.3 or 2.1.X series will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3 or 2.1.X, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

9d4def981900b5c62c3964841ca3e8cc *ruby-2.0.0-p645-doc-chm.7z
1a59c016a3ea0714b06d7a5f6aa4157a *ruby-2.0.0-p645-i386-mingw32.7z
d57d539b90f5bbf26550a9d1a3c33c33 *ruby-2.0.0-p645-x64-mingw32.7z
99923a423cb165f1ae0b040f736094ae *rubyinstaller-2.0.0-p645-x64.exe
355bc34a71914c2e8b2a2710227431c3 *rubyinstaller-2.0.0-p645.exe

SHA256:

e4796cc0492b29c6fc5e416c1d573f5ebdca2a0faf7c7fbaa30a9f72a7fe99b1 *ruby-2.0.0-p645-doc-chm.7z
b80146dffa97b654b54b5be3dac07f2140e3abada4707994bbd0455827977196 *ruby-2.0.0-p645-i386-mingw32.7z
cec14b304bd83e206426cf1d2edd31f37b41b90fdba69fe7b4c0b2d40a312ba3 *ruby-2.0.0-p645-x64-mingw32.7z
878dfe29fe644f64de02136df736709cf5ba620d617060eea732805cc9cae2ca *rubyinstaller-2.0.0-p645-x64.exe
9bfb1dfc6e24731570635ed39316a3f4541b12bf4b133605e51cfe577838cdc8 *rubyinstaller-2.0.0-p645.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 645
2.2.1 (Mar 05, 2015)

Ruby 2.2.1

Packages will be provided in two versions:
32bits (x86) and 64bits (x64).

Same DevKit used for version 2.0.0 is required for this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you understand that not all gems, libraries or tools have been tested for this version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there is no performance issue around it.

Ruby 2.2.x is brand new

While officially 2.2.x is stable, that doesn't mean all the software will magically work on it.

This is also the first 2.2.x release of a RubyInstaller package.
For possible issues please see the results of make check:
https://gist.github.com/Azolo/442a4dfdd259986d043d

Use 2.2.1 for development and verify your application, scripts and tools works properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.2 compatible

Ruby 2.2 introduced some C API changes which means compiled C extensions with previous versions of Ruby may not run against Ruby 2.2.

DO NOT install Ruby 2.2 on top of existing Ruby 2.1.x or earlier, or try to use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and 'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

b4d3fceaba0ba5c483fa877b9ebc285b *ruby-2.2.1-doc-chm.7z
9f1beca535b2e60098d826eb7cb1b972 *ruby-2.2.1-i386-mingw32.7z
0e6fe9f27367123f738bf143f4bf04f6 *ruby-2.2.1-x64-mingw32.7z
0c5323f7379574625dd3a7b3a4415349 *rubyinstaller-2.2.1-x64.exe
a569c153f7b1b23638038a34cdb9d9d6 *rubyinstaller-2.2.1.exe

SHA256

8e8fd759b7ea5ce6141da913d2ac528153a6a608ac82466f511aa59687c73a4c *ruby-2.2.1-doc-chm.7z
53c3d758f8be083abc00ce8c9f6150c007a93934e8b26647915ba2edef84a8e5 *ruby-2.2.1-i386-mingw32.7z
afc01c6e5fa15bfd32b85ab42f0466fbb5b7c74b08e9ed71f5ad2e852c979ecc *ruby-2.2.1-x64-mingw32.7z
6a0582505da6bcd30b2b8d5ab84129ec2ee23829aa932f7536dd70965ba0f9f2 *rubyinstaller-2.2.1-x64.exe
b2d8d93ce8179834916d2479a2e08bd900ec4a4df9070a9ba41b8b4cce36ec4a *rubyinstaller-2.2.1.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.2 to 2.2.1
  • Upgraded OpenSSL to 1.0.1l
2.0.0-p643 (Feb 27, 2015)

Ruby 2.0.0-p634

This is the last ordinal release of Ruby 2.0.0.

Ruby 2.0.0 has gone into the state of the security maintenance phase.
This means there will be no more releases in the 2.0.0 series unless any
critical regressions or security issues are found.

See the Official Ruby 2.0.0-p643 release announcement for more details

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

Things are pretty close, however it is still our recommendation you use a 32bit release.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 and 2.1 introduced ABI breakage which means compiled C extensions from
releases in the 1.9.3 or 2.1.X series will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3 or 2.1.X, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

cfda5da05a3f7a9747ac5adb37d1792e *ruby-2.0.0-p643-doc-chm.7z
b66147c695ff3f63e33d0be15c663789 *ruby-2.0.0-p643-i386-mingw32.7z
431233f1761f0ace752477e5f917e480 *ruby-2.0.0-p643-x64-mingw32.7z
0910accaf881ca4316be95b4a68f16b0 *rubyinstaller-2.0.0-p643-x64.exe
8189270d01e8d1018389d4e55e94f808 *rubyinstaller-2.0.0-p643.exe

SHA256:

0987aaf19baed6f4754bfe46d45c0846ad2309c8e8f1ddf355627ad8baa663e5 *ruby-2.0.0-p643-doc-chm.7z
15924f3726e9c1960d661c97f21ef92d252e14cc96d0f4362056d52ee7149761 *ruby-2.0.0-p643-i386-mingw32.7z
049c310565fc11cc7f99e6145024ee6c36d5e1ac4b634bed1b22fa3e3d3662cd *ruby-2.0.0-p643-x64-mingw32.7z
d993e82cb7414db82fcd3e8ab2582c684924e73dcec418c550bde126782fcacf *rubyinstaller-2.0.0-p643-x64.exe
0074e95e6573895a4e7742070d042c067a334d1ce4a2aba3e7b3f2a306dcc1ef *rubyinstaller-2.0.0-p643.exe

Official Announcement:

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 643
  • Update README to be in Markdown format
2.1.5 (Nov 16, 2014)

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.1.x is brand new

While officially 2.1.x is stable, that doesn't mean all the software will
magically work on it.

Use 2.1.4 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.1 compatible

Ruby 2.1 introduces ABI breakage which means compiled C extensions with previous
1.9.3 or 2.0.0 will not run against Ruby 2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 1.9.3 or 2.0.0, or try to
use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

e7aa15e80d4bf69353674a2789acea29 *ruby-2.1.5-doc-chm.7z
fe6b596fc47f503b0c0c01ebed16cf65 *ruby-2.1.5-i386-mingw32.7z
2ebc791db99858a0bd586968cddfcf0d *ruby-2.1.5-x64-mingw32.7z
eacd2526ef61fb73c0e642828675e94d *rubyinstaller-2.1.5.exe
3aad5fbfe6bfcf9cf3237ed9f048b81f *rubyinstaller-2.1.5-x64.exe

SHA256

ad9bc5a42cf92eecdf5959acb953302590b059d3aee3cc8092ef62ea9ea48492 *ruby-2.1.5-doc-chm.7z
1e1619d41ffae46826bb7866f9e6f148cf13730c40aba80e520f835ccd005f18 *ruby-2.1.5-i386-mingw32.7z
120dc70369c90ae66e3c02f1c9e70579841ab204a3eac1b25110d9ae542199a7 *ruby-2.1.5-x64-mingw32.7z
a426347e609e5502357443113d88c3c6274137bdab9af3f0f4aaf04b7f177c9f *rubyinstaller-2.1.5.exe
2464522a6cee84b51b8dd0cf5f8b87bd35da77d416305ead30b63923d4501f8f *rubyinstaller-2.1.5-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/11/13/ruby-2-1-5-is-released/

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.5
  • Upgraded OpenSSL to version 1.0.0o
2.0.0-p598 (Nov 16, 2014)

Ruby 2.0.0-p598

This new version of Ruby also brings new changes to RubyInstaller.

Starting with 2.0.0, the packages will be provided in two versions:
32bits (x86) and 64bits (x64).

This is possible thanks to newer compiler provided by mingw-w64 project.

This means newer DevKit package is required to use with this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.0.0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software will
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with previous
1.9.3 will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

1101f91b9d150e18a7f5052c360b2fbc *ruby-2.0.0-p598-doc-chm.7z
a4b7f5c3d3286b51ea35d34fde8aa174 *ruby-2.0.0-p598-i386-mingw32.7z
011b3832b6e557e7b25fd98821e28e69 *ruby-2.0.0-p598-x64-mingw32.7z
62c3873345b0f5f4ca8300ff705e2f38 *rubyinstaller-2.0.0-p598.exe
649e86af63afc48308110e838cbdfa6f *rubyinstaller-2.0.0-p598-x64.exe

SHA256

8fa2fa102fdd5c5424610345b437d44e34a90553ad34974c26219ee8768b7ec1 *ruby-2.0.0-p598-doc-chm.7z
7e62a1f06e198152c08ab13086e79b1c7807fecdd655593dd10c564d8f9b19b5 *ruby-2.0.0-p598-i386-mingw32.7z
5c5fc637923dbac5ace349f6e808562b74b6bab441b2a14a61a5ebde32936420 *ruby-2.0.0-p598-x64-mingw32.7z
aaa1bbb9bdb1e85da8675635956de53a6cd5c151ba32fceb72bb6366f2da8d92 *rubyinstaller-2.0.0-p598.exe
6e7ff2632f92af99d5c1dabb5e510b025ac8221deed0454b49f05a2a2b5d210f *rubyinstaller-2.0.0-p598-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/11/13/ruby-2-0-0-p598-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 598
  • Upgraded OpenSSL to version 1.0.0o
1.9.3-p551 (Nov 16, 2014)

1.9.3-p551

Important

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Maintenance notice

Ruby 1.9.3 is now in the security maintenance phase. This means that we
never fix bugs except about security issues. And, at this time, the end
of the maintenance of 1.9.3 has been scheduled for February next year. We
recommend that users of Ruby 1.9.3 should migrate to a newer version as
soon as possible.

MD5:

59cce15a7da23d7578e5ee84e329dd74 *ruby-1.9.3-p551-doc-chm.7z
73ba6e292d3afec5cecc68ec64fd85bf *ruby-1.9.3-p551-i386-mingw32.7z
25de5ff94b76d7d308cb75ba8179a6c0 *rubyinstaller-1.9.3-p551.exe

SHA256:

c6e9c67420ed8039b76f243dacc0b56232693d3f520b60668d2bd4348a11bb9e *ruby-1.9.3-p551-doc-chm.7z
207fdb5b2f9436ad1ac27bf51918b913c14c443d1b83cd910cf5a59acaeab756 *ruby-1.9.3-p551-i386-mingw32.7z
d0c5cffb7215999568c18f4221b3ec41bfc5ddd374f8b30381a353f4d97f2f30 *rubyinstaller-1.9.3-p551.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/11/13/ruby-1-9-3-p551-is-released/

Enhancements:

  • Upgraded Ruby 1.9.3 to patchlevel 551
  • Upgraded OpenSSL to version 1.0.0o
2.1.4 (Oct 29, 2014)

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.1.x is brand new

While officially 2.1.x is stable, that doesn't mean all the software will
magically work on it.

Use 2.1.4 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.1 compatible

Ruby 2.1 introduces ABI breakage which means compiled C extensions with previous
1.9.3 or 2.0.0 will not run against Ruby 2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 1.9.3 or 2.0.0, or try to
use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

df20891e25c1b72fe9f66a9ba95dd7e7 *ruby-2.1.4-doc-chm.7z
fcfba33c49495371dbe24d4534a286ff *ruby-2.1.4-i386-mingw32.7z
debe002022929b0afff5bad8f4d5039c *ruby-2.1.4-x64-mingw32.7z
cba755c388c2254d0182b00dc0726dd0 *rubyinstaller-2.1.4-x64.exe
56ce24a6bd422adb3e21b903cc1818cf *rubyinstaller-2.1.4.exe

SHA256

df8b6c928672ab85b83ba1cd123ca0a932e3a691496c320f7919a89ea7b52f10 *ruby-2.1.4-doc-chm.7z
a0909ee86b8e2492e3696f4a7decd9dbe041562cdf66a5bc0080c239e68ca7fe *ruby-2.1.4-i386-mingw32.7z
c6148c9521cd167c1c8eff4b14bf8caba079cccc4f7e8c5e00e7299f3cca2ab3 *ruby-2.1.4-x64-mingw32.7z
7abd94bb78f3dbecbb02a2370b05cdbd1dbf176afe887b66c742f506cf32472a *rubyinstaller-2.1.4-x64.exe
1155b8eab79f6818ae4b09fec6a180da31c8bed6f81c3747ce5a6434b37c6d86 *rubyinstaller-2.1.4.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/10/27/ruby-2-1-4-released/

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.4
2.0.0-p594 (Oct 28, 2014)

Ruby 2.0.0-p594

This new version of Ruby also brings new changes to RubyInstaller.

Starting with 2.0.0, the packages will be provided in two versions:
32bits (x86) and 64bits (x64).

This is possible thanks to newer compiler provided by mingw-w64 project.

This means newer DevKit package is required to use with this version.

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.0.0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software will
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with previous
1.9.3 will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

9b89cb76941f1ffb821b9cc829644503 *ruby-2.0.0-p594-doc-chm.7z
fa132c0c7965b159f3770002d0138e83 *ruby-2.0.0-p594-i386-mingw32.7z
6e9bdafb2793e6b1d9ffc672235dc6d6 *ruby-2.0.0-p594-x64-mingw32.7z
f55531333d99e7264005088f786e1a64 *rubyinstaller-2.0.0-p594-x64.exe
b42ae989e0faadb0fd47ff2e65d7995f *rubyinstaller-2.0.0-p594.exe

SHA256

ae9ded24b60c748d12e54a61ab7c2eec2a7cac9c9dca74890e8cd5c9694fdf98 *ruby-2.0.0-p594-doc-chm.7z
f64fe7471c84f62db9600a75b80be6cc5dfcf2c0280bcd3eb2ad6c454728dc53 *ruby-2.0.0-p594-i386-mingw32.7z
0089d780afad6762d0dbfff17b96bf2f65b4195aa506cfca31f4e380c2612fcb *ruby-2.0.0-p594-x64-mingw32.7z
d4f1983d8034e1ac737f7438ae8286771597f6ee09a168058ac3ee762b978076 *rubyinstaller-2.0.0-p594-x64.exe
7cedaed26ddcbf53ddae69ccce9b1171e3558fe3f49cf052b71b5f27b06ad1d7 *rubyinstaller-2.0.0-p594.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/10/27/ruby-2-0-0-p594-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 594
1.9.3-p550 (Oct 28, 2014)

1.9.3-p550

Important

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Maintenance notice

Ruby 1.9.3 is now in the security maintenance phase. This means that we
never fix bugs except about security issues. And, at this time, the end
of the maintenance of 1.9.3 has been scheduled for February next year. We
recommend that users of Ruby 1.9.3 should migrate to a newer version as
soon as possible.

MD5:

f433b16162585c9f70e2d3a153035b16 *ruby-1.9.3-p550-doc-chm.7z
e75746ee30fc7291e9128d881e0414e2 *ruby-1.9.3-p550-i386-mingw32.7z
8e235218804893eca689d5542bf3fc0d *rubyinstaller-1.9.3-p550.exe

SHA256:

e835fdffc2f76764d3bbc661d7a6f8eba827b1a1787956534227988c71232221 *ruby-1.9.3-p550-doc-chm.7z
779aaeea987a2d7523f4e18531ffc2bf83e0d0b486ebb0b8f05679076a32ebfa *ruby-1.9.3-p550-i386-mingw32.7z
775d8bd9a102a1f7a113cfe200833f73649702337f31c363da0187de4ec6f22d *rubyinstaller-1.9.3-p550.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/10/27/ruby-1-9-3-p550-is-released/

Enhancements:

  • Upgraded Ruby 1.9.3 to patchlevel 550
  • Upgraded RubyGems to version 1.8.29
  • Upgraded OpenSSL to version 1.0.0n
  • Upgraded zlib to version 1.2.8
2.0.0-p576 (Sep 19, 2014)

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.0.0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software will
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with previous
1.9.3 will not run against Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

15226e34ddb8b208b78ac12440c9e23c *ruby-2.0.0-p576-doc-chm.7z
40a87864ca89bbd46f8083bb5cd52d89 *ruby-2.0.0-p576-i386-mingw32.7z
a097cb750316e8bfa25fd836dd4296fa *ruby-2.0.0-p576-x64-mingw32.7z
723ae8cda24a86c16914582a340deece *rubyinstaller-2.0.0-p576.exe
a6ab3963c571055cba649237d3f4a771 *rubyinstaller-2.0.0-p576-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/09/19/ruby-2-0-0-p576-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 576
  • Upgraded OpenSSL to version 1.0.0n
  • Upgraded zlib to version 1.2.8
2.1.3 (Sep 20, 2014)

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.1.x is brand new

While officially 2.1.x is stable, that doesn't mean all the software will
magically work on it.

Use 2.1.3 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.1 introduces ABI breakage which means compiled C extensions with previous
1.9.3 or 2.0.0 will not run against Ruby 2.1.

DO NOT install Ruby 2.1 on top of existing Ruby 1.9.3 or 2.0.0, or try to
use compiled extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of another version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby

Known Issues

There are some issues with Development Kit configuration process that fails
to detect x64 installations of Ruby. You will need to manually edit
config.yml for it to work. See the following issues for details:

MD5:

594509a374a48fe05598ec203c62f782 *ruby-2.1.3-doc-chm.7z
60e39aaab140c3a22abdc04ec2017968 *ruby-2.1.3-i386-mingw32.7z
d339f956db4d4b1e8a30ac3e33014844 *ruby-2.1.3-x64-mingw32.7z
e5e2c028d76895e9da6c3c86965fc747 *rubyinstaller-2.1.3.exe
0f29131a6852cf92382c082eaf1dfd34 *rubyinstaller-2.1.3-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/09/19/ruby-2-1-3-is-released/

Enhancements:

  • Upgraded Ruby 2.1 to version 2.1.3
  • Upgraded OpenSSL to version 1.0.0n
  • Upgraded zlib to version 1.2.8
2.0.0-p481 (May 11, 2014)

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version (labeled x64), it is important you
understand that not all gems, libraries or tools have been tested for this
version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.0.0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software will
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with previous
1.9.3 will work with Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • For 32bits Ruby 2.0.0: download and install DevKit-mingw64-32-4.7.2
  • For 64bits Ruby 2.0.0: download and install DevKit-mingw64-64-4.7.2

MD5:

d8d9a776aa87edb3bc6727b8c185fabf *ruby-2.0.0-p481-doc-chm.7z
1a43404393f080e0225509415866307b *ruby-2.0.0-p481-i386-mingw32.7z
61a3f9d707ea3bf5af57de29d463b191 *ruby-2.0.0-p481-x64-mingw32.7z
3332ebb3fb91c34b7e4e2e198c2f16d1 *rubyinstaller-2.0.0-p481.exe
65a242aba15bf96253aa5b76d33a91de *rubyinstaller-2.0.0-p481-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/05/09/ruby-2-0-0-p481-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 481
  • Upgraded libyaml to version 0.1.6
2.0.0-p451 (Feb 25, 2014)

Important information

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

Choosing 32bits vs 64bits

Before you download a 64bits version, it is important you understand that
not all gems, libraries or tools have been tested for this version.

It is our recommendation you use 32bits until these issues are solved.

If you have a 64bits version of Windows, you can still use 32bits, as there
is no performance issue around it.

Ruby 2.0.0 is brand new

While officially 2.0.0 is stable, that doesn't mean all the software will
magically work on it.

Use 2.0.0 for development and verify your application, scripts and tools works
properly before deciding to run this in your production environment.

Existing pre-compiled gems might not be Ruby 2.0 compatible

Ruby 2.0 introduces ABI breakage which means compiled C extensions with previous
1.9.3 will work with Ruby 2.0.

DO NOT install Ruby 2.0 on top of existing Ruby 1.9.3, or try to use compiled
extensions with it.

You will be required to force compilation of those gems:

gem install <name> --platform=ruby

This will require you have the extra dependencies installed for that gem to
compile. Look at the gem documentation for the requirements.

Please check each gem documentation and recent releases.

Do not use other DevKit version than the one recommended

This version of Ruby has been compiled and optimized for mingw-w64 GCC 4.7.2.

Use of older version of DevKit package to compile gems might result in
compilation issues during gem installation or simply segfaults.

Look for the DevKit installers identified with the name 'DevKit-mingw64-32' and
'DevKit-mingw64-64' for 32 and 64 bits respectively.

To be clear:

  • Download and install DevKit-mingw64-32-4.7.2 for 32bits Ruby 2.0.0
  • Download and install DevKit-mingw64-64-4.7.2 for 64bits Ruby 2.0.0

MD5:

4ee9c69517ad11b2b43f2aa3fb798f45 *ruby-2.0.0-p451-doc-chm.7z
37feadb0230e7f475a8591d1807ecfec *ruby-2.0.0-p451-i386-mingw32.7z
d4f6741138a26a4be12e684a16a19b75 *ruby-2.0.0-p451-x64-mingw32.7z
9638024ea8a9095a70a4c521dd2ec2f6 *rubyinstaller-2.0.0-p451.exe
af94b61c7113b79ae548d3363e59e5f1 *rubyinstaller-2.0.0-p451-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/02/24/ruby-2-0-0-p451-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 451
  • Upgraded rb-readline to 0.5.0 (compatible with Ruby 2.0)
  • Upgraded OpenSSL to version 1.0.0l
  • Upgraded libyaml to version 0.1.5
1.9.3-p545 (Feb 25, 2014)

1.9.3-p545

Important

Please note that the installers in this release are not digitally signed.

You can read more about this in post at RubyInstaller group:
https://groups.google.com/d/topic/rubyinstaller/NhAqcepQ-Xw/discussion

MD5:

2a1fd8bee3c1a605688892020d44c8ca *ruby-1.9.3-p545-doc-chm.7z
8e7f07256c86bfd6fc73fbcc13db4b09 *ruby-1.9.3-p545-i386-mingw32.7z
05398a6cd920ccd297c28150a935ef72 *rubyinstaller-1.9.3-p545.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2014/02/24/ruby-1-9-3-p545-is-released/

Enhancements:

  • Upgraded Ruby 1.9.3 to patchlevel 545
  • Upgraded rb-readline to 0.5.0 (compatible with Ruby 2.0)
  • Upgraded OpenSSL to version 1.0.0l
  • Upgraded libyaml to version 0.1.5
2.0.0-p353 (Nov 24, 2013)

2.0.0-p353

Important

Please note that the installers in this release are not digitally signed.

You can read more about this in RubyInstaller post

MD5:

640b865ccade8f14928677480696d123 *ruby-2.0.0-p353-doc-chm.7z
a5795f7232c4b9ebf048fa6380f1f442 *ruby-2.0.0-p353-i386-mingw32.7z
c4b0ed0e084fa1f8b6eedb2d7b45c2a7 *ruby-2.0.0-p353-x64-mingw32.7z
ff10e6a238199117dea7ef4fe8a5c73c *rubyinstaller-2.0.0-p353.exe
b31faf2c80f22c3babb5e4fbc4380dbc *rubyinstaller-2.0.0-p353-x64.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2013/11/22/ruby-2-0-0-p353-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 353
1.9.3-p484 (Nov 24, 2013)

1.9.3-p484

Important

Please note that the installers in this release are not digitally signed.

You can read more about this in RubyInstaller post

MD5:

2874cf0770a014cc673f62c85f6924d9 *ruby-1.9.3-p484-doc-chm.7z
a0665113aaeea83f1c4bea02fcf16694 *ruby-1.9.3-p484-i386-mingw32.7z
426cf2669414b4689413c7a838684619 *rubyinstaller-1.9.3-p484.exe

Official Announcement:

https://www.ruby-lang.org/en/news/2013/11/22/ruby-1-9-3-p484-is-released/

Enhancements:

  • Upgraded Ruby 1.9.3 to patchlevel 484
  • Upgraded RubyGems to version 1.8.28
2.0.0-p247 (Jul 07, 2013)

2.0.0-p247

MD5:

5dfbb0e6c056112258ac23308912aec6 *ruby-2.0.0-p247-doc-chm.7z
6330679d26dd16b6648ca4bdbb95704d *ruby-2.0.0-p247-i386-mingw32.7z
e1d2a2d67808ee9a7a0171aca1ffa80e *ruby-2.0.0-p247-x64-mingw32.7z
8968214a1f1b2eba4f18436a1863832c *rubyinstaller-2.0.0-p247.exe
48c0773f56c6983f005a41ca510a4661 *rubyinstaller-2.0.0-p247-x64.exe

Official Announcement:

http://www.ruby-lang.org/en/news/2013/06/27/ruby-2-0-0-p247-is-released/

Enhancements:

  • Upgraded Ruby 2.0.0 to patchlevel 247
1.9.3-p448 (Jul 07, 2013)

1.9.3-p448

MD5:

b3f4dc603df6b5fba6867a2012a95d83 *ruby-1.9.3-p448-doc-chm.7z
e317c1225ccf9fdeba951186f2a546aa *ruby-1.9.3-p448-i386-mingw32.7z
bcb46cc7a6f570692d15ac4b0d99dbf6 *rubyinstaller-1.9.3-p448.exe

Official Announcement:

http://www.ruby-lang.org/en/news/2013/06/27/ruby-1-9-3-p448-is-released/

Enhancements:

  • Upgraded Ruby 1.9.3 to patchlevel 448
1.9.2-p290 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p374 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p286 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p429 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p334 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p358 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p327 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p371 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p302 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p357 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p330 (Feb 12, 2015)
No release notes available for this version yet.
1.9.2-p136 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p362 (Feb 12, 2015)
No release notes available for this version yet.
2.0.0-p0 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p125 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p374 (Jul 07, 2013)

1.8.7-p374

DEPRECATION NOTICE: As June 2013, Ruby 1.8.7 has been retired and no
longer maintained. It is recommended you upgrade your applications to a newer
version of Ruby.

MD5:

bbf8dacba3dd221856bdab4afa61c76a *ruby-1.8.7-p374-doc-chm.7z
2eabeb3bb210d088083c0c04fdf94c7e *ruby-1.8.7-p374-i386-mingw32.7z
2e33a098f126275f7cb29ddcd0eb9845 *rubyinstaller-1.8.7-p374.exe

Official Announcement:

http://www.ruby-lang.org/en/news/2013/06/27/ruby-1-8-7-p374-is-released/

Enhancements:

  • Upgraded Ruby 1.8.7 to patchlevel 374
  • Upgraded OpenSSL to version 1.0.0k
  • Upgraded rb-readline to 0.5.0.pre.1 (compatible with Ruby 2.0)
1.9.2-p180 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p385 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p392 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p352 (Feb 12, 2015)
No release notes available for this version yet.
1.9.2-p0 (Feb 12, 2015)
No release notes available for this version yet.
1.8.7-p370 (Feb 12, 2015)
No release notes available for this version yet.
2.0.0-p195 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p194 (Feb 12, 2015)
No release notes available for this version yet.
1.9.3-p0 (Feb 12, 2015)
No release notes available for this version yet.