|
| 1 | +--- |
| 2 | +title: April 2025 RubyGems Updates |
| 3 | +layout: post |
| 4 | +author: Gift Egwuenu |
| 5 | +author_email: laurandidi21@gmail.com |
| 6 | +--- |
| 7 | + |
| 8 | +Welcome to the RubyGems monthly update! As part of our efforts at Ruby Central, we publish a recap of the work that we’ve done the previous month. Read on to find out what updates were made to RubyGems and RubyGems.org in April. |
| 9 | + |
| 10 | +## RubyGems News |
| 11 | + |
| 12 | +In April, we released RubyGems [**3.6.7**](https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md#367--2025-04-03), [**3.6.8**](https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md#368--2025-04-13) and Bundler [**2.6.7**](https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#267-april-3-2025), [**2.6.8**](https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#268-april-13-2025). These releases bring a series of enhancements and bug fixes designed to improve the overall developer experience with RubyGems. |
| 13 | + |
| 14 | +Notable improvements include [defaulting to a `SOURCE_DATE_EPOCH` of `315619200`](https://github.com/rubygems/rubygems/pull/8568) to simplify reproducible builds, [sorting gemspec metadata fields](https://github.com/rubygems/rubygems/pull/8569) to support consistent build outputs, [fixing a crash when the compact index API only listed versions](https://github.com/rubygems/rubygems/pull/8594), and [speeding up `Gem::Version#<=>` comparisons by 20–50%](https://github.com/rubygems/rubygems/pull/8565) when version lengths differ. |
| 15 | + |
| 16 | +Some other important accomplishments from the team this month include: |
| 17 | + |
| 18 | +**Progress on gems with precompiled binaries** |
| 19 | + |
| 20 | +- Following community interest and questions about the initial **“wheels” proposal**, We opened a [GitHub discussion](https://github.com/rubygems/rubygems/discussions/8645) to gather feedback and facilitate conversation. We also invited input from members of the **OpenSSF Securing Software Repositories Working Group** to help align Ruby’s approach with best practices from other language ecosystems. |
| 21 | +- We are now focused on collecting ****this feedback into a concrete list of features that will make it easier to use and develop gems with precompiled binaries, guiding the future of RubyGems in this space. |
| 22 | + |
| 23 | +**Development of a Bundler 4 roadmap** |
| 24 | + |
| 25 | +- [The Bundler 4 roadmap has been drafted](https://github.com/rubygems/rubygems/issues/8650), aiming to consolidate over a decade of unreleased improvements and breaking changes into a major release. |
| 26 | +- The plan is to review and discuss all pending changes, allow users to opt-in and provide feedback, and prepare for a big release in December. This marks an important step toward modernizing Bundler while giving the community a clear path forward. |
| 27 | + |
| 28 | +**`bundle doctor` now troubleshoots SSL issues** |
| 29 | + |
| 30 | +- The `bundle doctor` command [now includes a new `--ssl` flag](https://github.com/rubygems/rubygems/pull/8624) to help users diagnose SSL-related issues. This improvement brings the functionality of the previously separate [ruby-ssl-check script](https://github.com/rubygems/ruby-ssl-check) directly into Bundler, making it easier to maintain and more accessible to users. |
| 31 | +- Thanks to [@Edouard-chin](https://github.com/Edouard-chin) for contributing this enhancement by porting the script and integrating it into `bundle doctor`. |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | +## RubyGems.org News |
| 36 | + |
| 37 | +The updates made this month to [RubyGems.org](http://rubygems.org/) reflect a strong commitment to improving user experience, enhancing security, and modernizing the platform. Sponsored hosting for RubyGems.org in April was provided by [AWS](https://aws.amazon.com/?ref=rubycentral.org), [Fastly](https://www.fastly.com/?ref=rubycentral.org) and [Datadog](https://www.datadoghq.com/?ref=rubycentral.org). |
| 38 | + |
| 39 | +**April 2025 RubyGems stats** |
| 40 | + |
| 41 | +In April 2025, RubyGems.org recorded over **4.15 billion total gem downloads**, a **51% increase** from 2.74 billion in April 2024. This marks the first time in history that monthly gem downloads surpassed the **4 billion mark**, highlighting the continued momentum and growing impact of the Ruby ecosystem. Thanks to all of our partners and sponsors helping this to happen! |
| 42 | + |
| 43 | +Looking at Bundler gem downloads trends, usage data shows a clear shift towards modern Ruby versions: |
| 44 | + |
| 45 | +- **Ruby 3.4**, released in December 2024, already accounts for **13.1%** of Bundler downloads. |
| 46 | +- **Ruby 3.3** rose from **10.4% to 27.9%**, making it the most widely used version. |
| 47 | +- **Ruby 3.2** declined from **28.1% to 21.8%**, while **Ruby 3.1,** which reached EOL in March 2025, fell from **24.8% to 14.1%**. |
| 48 | +- **Ruby 2.7**, EOL since March 2023, dropped from **20.4% to 16.1%**. |
| 49 | +- Older versions (2.6 and below) continued their gradual decline. |
| 50 | + |
| 51 | +These trends reflect a strong migration toward actively maintained, supported Ruby versions. Analytics were powered by ****[Clickhouse](https://clickhouse.com/). |
| 52 | + |
| 53 | +The following are highlights of what the team worked on this month: |
| 54 | + |
| 55 | +**Progress update on organizations** |
| 56 | + |
| 57 | +- Work has resumed on the long-anticipated **Organizations feature** in RubyGems.org, led by [Colby Swandale](https://github.com/colby-swandale). After identifying the remaining functionality a few months ago, we’ve now secured budget to complete the work. |
| 58 | +- The feature is currently being demoed to a small group of beta testers, with plans to open it to the broader community in the future. We’re looking forward to gathering feedback once Organizations becomes publicly available. |
| 59 | + |
| 60 | +## Thank you |
| 61 | + |
| 62 | +A huge thank you to all the contributors to RubyGems and [RubyGems.org](http://rubygems.org/) this month! We deeply appreciate your support and dedication. |
| 63 | + |
| 64 | +### Contributors to RubyGems: |
| 65 | + |
| 66 | +- [@deivid-rodriguez](https://github.com/deivid-rodriguez) David Rodríguez |
| 67 | +- [@Edouard-chin](https://github.com/Edouard-chin) Edouard Chin |
| 68 | +- [@hsbt](https://github.com/hsbt) Hiroshi Shibata |
| 69 | +- [@jeremyevans](https://github.com/jeremyevans) Jeremy Evans |
| 70 | +- [@martinemde](https://github.com/martinemde) Martin Emde |
| 71 | +- [@mperham](https://github.com/mperham) Mike Perham |
| 72 | +- [@nobu](https://github.com/nobu) Nobuyoshi Nakada |
| 73 | +- [@thatrobotdev](https://github.com/thatrobotdev) James Kerrane |
| 74 | +- [@segiddins](https://github.com/segiddins) Samuel Giddins |
| 75 | +- [@simi](https://github.com/simi) Josef Šimánek |
| 76 | +- [@skipkayhil](https://github.com/skipkayhil) Hartley McGuire |
| 77 | + |
| 78 | +### Contributors to [RubyGems.org](http://rubygems.org/): |
| 79 | + |
| 80 | +- [@colby-swandale](https://github.com/colby-swandale) Colby Swandale |
| 81 | +- [@gingerwizard](https://github.com/gingerwizard) Dale McDiarmid |
| 82 | +- [@hsbt](https://github.com/hsbt) Hiroshi Shibata |
| 83 | +- [@indirect](https://github.com/indirect) André Arko |
| 84 | +- [@marcoroth](https://github.com/marcoroth) Marco Roth |
| 85 | +- [@martinemde](https://github.com/martinemde) Martin Emde |
| 86 | +- [@segiddins](https://github.com/segiddins) Samuel Giddins |
| 87 | +- [@simi](https://github.com/simi) Josef Šimánek |
| 88 | + |
| 89 | +*If we missed you, please let us know so we can include you in our shout out!* |
| 90 | + |
| 91 | +--- |
| 92 | +Learn more about contributing to RubyGems by visiting the RubyGems Contributing Guide. We welcome all kinds of contributions, including bug fixes, feature implementation, writing and updating documentation, and bug triage. |
0 commit comments