惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

G
Google Developers Blog
阮一峰的网络日志
阮一峰的网络日志
IT之家
IT之家
人人都是产品经理
人人都是产品经理
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
博客园 - 【当耐特】
WordPress大学
WordPress大学
Hugging Face - Blog
Hugging Face - Blog
博客园 - 叶小钗
罗磊的独立博客
宝玉的分享
宝玉的分享
月光博客
月光博客
V
V2EX
博客园 - 司徒正美
Vercel News
Vercel News
量子位
Y
Y Combinator Blog
美团技术团队
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
T
Tailwind CSS Blog
博客园 - Franky
小众软件
小众软件
I
InfoQ
A
About on SuperTechFans

RubyInstaller for Windows

Ruby-4.0 is available in the Microsoft Store RubyInstaller 3.4.1-2 released with a new package for ARM64 Ruby Version Manager 4 Windows 1.0.0 released RubyInstaller for ARM64 RubyInstaller 3.3.0-1 released RubyInstaller 3.2.1-1 released RubyInstaller 3.2.0-1 released RubyInstaller 3.1.3-1, 3.0.5-1 and 2.7.7-1 released RubyInstaller 3.1.2-1, 3.0.4-1, 2.7.6-1 and 2.6.10-1 released
RubyInstaller 3.2.2-1, 3.1.4-1, 3.0.6-1 and 2.7.8-1 released
Lars Kanis · 2023-04-01 · via RubyInstaller for Windows

RubyInstaller versions 3.2.2-1, 3.1.4-1, 3.0.6-1 and 2.7.8-1 are released. These are maintenance releases with bug and security fixes. See the ruby-3.2.2 release post, ruby-3.1.4 release post, ruby-3.0.6 release post and ruby-2.7.8 release post for more details about the ruby core update.

In addition to the ruby core updates there are several changes to RubyInstaller. The RubyInstaller versions 3.1.4-1, 3.0.6-1 and 2.7.8-1 are now updated to the changes already introduced by 3.2.x. That means that the installer now offers an all-users installation with gem installation into the user home directories. The single user mode is still recommended unless you want to actually use Ruby by several users on the same system. See the wiki for more details about the install modes and the CHANGELOGs for more changes to the ruby installation.

As always: a previous RubyInstaller-2.7.x to 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. It’s best to use a new directory for each minor version as proposed by the installer.

All binaries are available in the Download section!