RubyInstallers Archives
Not sure what version to download? Please read the right-hand column for recommendations.
with Devkit
-
Ruby+Devkit 3.3.1-1 (x64)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.3.1-1 (x86)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.2.4-1 (x64)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.2.4-1 (x86)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.1.5-1 (x64)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.1.5-1 (x86)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.0.7-1 (x64)
- download PGP signature
- SHA256:
-
Ruby+Devkit 3.0.7-1 (x86)
- download PGP signature
- SHA256:
without Devkit
Other Useful Downloads
7-Zip Archives
PGP signature key
🔑 ci.ri2-package-signing-key.asc
See the Wiki how to verify PGP signatures.
Which version to download?
If you don’t know what version to install and you’re getting started with Ruby, we recommend that you use the Ruby+Devkit 3.2.X (x64) installer. It provides the biggest number of compatible gems and installs the MSYS2 Devkit alongside Ruby, so gems with C-extensions can be compiled immediately. The 32 bit (x86) version is not recommended, unless custom 32 bit native DLLs or COM objects have to be used.
How to update?
Ruby can be updated to the latest patch version (e.g. from 3.1.0 to 3.1.3) by running the new installer version.
Installed gems are not overwritten and will work with the new version without re-installation.
It’s sufficient to use the RubyInstaller without Devkit for these update installations.
The Devkit can be updated separately using the ridk install
command.
If the new Ruby version is from a different stable branch, then please use a new target directory for installation. That is to say, a previous RubyInstaller-3.1.x installation should not be updated by installing RubyInstaller-3.2.x into the same directory. This is because gems with C extensions are not compatible between ruby-3.1 and 3.2. Find out more in the FAQ.
RubyInstaller-head
RubyInstaller-head is a daily-updated version of the Ruby development branch. It can be used for continuous integration tests (CI) on your gems or applications, so you’re prepared for upcoming changes to the Ruby core. Builds are available on stable download URIs in the github release section. They can be easily integrated into Github Actions or Appveyor.
With Development Kit?
RubyInstaller uses the MSYS2 toolchain as its development kit. It is bundled into the Ruby+Devkit installer version as a selectable component, so that no additional downloads/installs are required. It’s possible to share one Devkit among multiple versions of Ruby.
MSYS2 is required in order to build native C/C++ extensions for Ruby and is necessary for Ruby on Rails. Moreover it allows the download and usage of hundreds of Open Source libraries which Ruby gems often depend on.
The MSYS2 development environment can be activated in a running cmd
or powershell console by ridk enable
.
This adds commands like make
, gcc
, pacman
or sh
to the search path.
See more in the Wiki.
Speed and Convenience
RubyInstaller is compiled with the latest GCC at the release date. The installed Ruby is a native Windows application but combines this with the rich UNIX toolset of MSYS2 and the large repository of MINGW libraries.
Read more about RubyInstaller and its alternatives here.
Documentation
The Ruby core- and standard library documentation are included as part of the installation. We also recommend the online documentation, or the HTML version downloadable from ruby-doc.org.
Support
Enjoy! Happy Ruby-coding! And let us know what you think, or if you have any issues, at our helpful and friendly RubyInstaller Google Group.