Skip to content

Commit fe1c4e0

Browse files
lauragift21lauragift21
authored
Merge pull request #182 from rubygems/feb-2024-updates
Publish February 2024 RubyGems Monthly Update
2 parents 81740fe + b1a1ba4 commit fe1c4e0

2 files changed

Lines changed: 98 additions & 6 deletions

File tree

‎_posts/2024-02-17-january-rubygems-updates.md‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ Welcome to the RubyGems monthly update! As part of our efforts at Ruby Central,
99

1010
## RubyGems News
1111

12-
In January in RubyGems, we released RubyGems [3.5.5](https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md#355--2024-01-18) and Bundler [2.5.5](https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#255-january-18-2024). These releases included fixes to: [the caching specifictions directory](https://github.com/rubygems/rubygems/pull/7331), [development dependency ommission](https://github.com/rubygems/rubygems/pull/7358) and [formatting of compact index requests headers](https://github.com/rubygems/rubygems/pull/7352), as part of our continuous effort to enhance the Ruby development experience.
12+
In January in RubyGems, we released RubyGems [3.5.5](https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md#355--2024-01-18) and Bundler [2.5.5](https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#255-january-18-2024). These releases included fixes for: [caching specifictions directory](https://github.com/rubygems/rubygems/pull/7331), [development dependency ommission](https://github.com/rubygems/rubygems/pull/7358) and [formatting of compact index requests headers](https://github.com/rubygems/rubygems/pull/7352), as part of our continuous effort to enhance the Ruby development experience.
1313

1414
Some other important accomplishments from the team this month include:
1515

@@ -35,6 +35,10 @@ Some other important accomplishments from the team this month include:
3535

3636
Restoring Bundler-related ENV variables to empty prevents downstream issues related to trying to invoke Bundler from subprocesses, as one of our users [Edouard-chin](https://github.com/Edouard-chin) pointed out. An investigation led to the identification of a bug related to special casing empty ENV variables. The decision was made to remove this exception and the fix. Its implications are detailed in [#7383](https://github.com/rubygems/rubygems/pull/7383).
3737

38+
- **Introduction of a Gem Rebuild Command**
39+
40+
[Ellen Dash](https://github.com/duckinator) is leading the development of a gem rebuild command to facilitate reproducible builds. Reproducible builds allow people to identify problems such as compromised build environments or builds not using the published source. For a few years now, it’s been technically possible to reproduce a build if you knew enough about the original build environment. The `gem rebuild` command’s purpose is to automate as much of this as possible.
41+
3842
In January, RubyGems gained [163 new commits](https://github.com/rubygems/rubygems/compare/master@%7B2024-1-01%7D...master@%7B2024-1-31%7D) contributed by 18 authors. There were 6,051 additions and 1,059 deletions across 244 files.
3943

4044
## RubyGems.org News
@@ -63,11 +67,7 @@ The following are highlights of what the team worked on this month:
6367

6468
We updated RubyGems.org to Rails 7.1 to keep dependencies of the Rails app up to date. The update involved a long-running pull request that addressed dependency issues. The merge and deployment proceeded smoothly after ensuring all upstream dependencies supported Rails 7.1, along with an update to the Rails configuration to align with 7.1 defaults.
6569

66-
- **Introduction of a Gem Rebuild Command**
67-
68-
[Ellen Dash](https://github.com/duckinator) is leading the development of a gem rebuild command to facilitate reproducible builds. Reproducible builds allow people to identify problems such as compromised build environments or builds not using the published source. For a few years now, it’s been technically possible to reproduce a build if you knew enough about the original build environment. The `gem rebuild` command’s purpose is to automate as much of this as possible.
69-
70-
In December, RubyGems.org gained [85 new commits](https://github.com/rubygems/rubygems.org/compare/master@%7B2024-1-01%7D...master@%7B2024-1-31%7D) contributed by 8 authors. There were 2,490 additions and 1,238 deletions across 224 files.
70+
In January, RubyGems.org gained [85 new commits](https://github.com/rubygems/rubygems.org/compare/master@%7B2024-1-01%7D...master@%7B2024-1-31%7D) contributed by 8 authors. There were 2,490 additions and 1,238 deletions across 224 files.
7171

7272
## Thank you
7373

‎_posts/2024-03-21-february-rubygems-updates.md‎

Lines changed: 92 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,92 @@
1+
---
2+
title: February 2024 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 February.
9+
10+
## RubyGems News
11+
12+
This month, RubyGems released RubyGems [3.5.6](https://github.com/rubygems/rubygems/blob/master/CHANGELOG.md#356--2024-02-06) and Bundler [2.5.6](https://github.com/rubygems/rubygems/blob/master/bundler/CHANGELOG.md#256-february-6-2024). These updates include enhancements such as [improved deep copy requirements in `Gem::Specification` and `Gem::Requirement` specifications](https://github.com/rubygems/rubygems/pull/7439), and [improvements to the gem login scope](https://github.com/rubygems/rubygems/pull/7342). These efforts are part of our ongoing commitment to improving the RubyGems development experience.
13+
14+
15+
Another accomplishment from the team this month:
16+
17+
**[Merging a new `gem rebuild` command](https://github.com/rubygems/rubygems/pull/4913)**
18+
- The goal of this feature was to help create a simplified version of gem rebuild command as a standalone tool, so reproducible builds are available for existing RubyGems versions (since RubyGems versions have to match a build to be reproduced properly). The process involved setting up reproducible gem builds as a default, and including the `Gem.source_date_epoch` value into the metadata of built gems.
19+
- The groundwork for this command involved a preliminary rebuild script to assess reproducibility requirements. Special thanks to [@duckinator](https://github.com/duckinator) for their significant contributions in developing this feature.
20+
21+
In February, RubyGems gained [97 new commits](https://github.com/rubygems/rubygems/compare/master@%7B2024-2-01%7D...master@%7B2024-2-31%7D) contributed by 16 authors. There were 691 additions and 329 deletions across 120 files.
22+
23+
24+
## RubyGems.org News
25+
26+
February’s updates to RubyGems.org reflect a strong commitment to improving user experience, enhancing security, and modernizing the platform.
27+
28+
The following are highlights of what the team worked on this month:
29+
30+
**Converted Rubygems.org to Importmap + Stimulus Controllers**
31+
32+
- The goal of adding stimulus controllers is to enable a modern, faster and simpler development experience for devs and bring us all the way to the most modern Rails default.
33+
- We introduced `importmaps` on RubyGems.org last month to set us up for adding stimulus controllers. This entailed [first creating a foundation for import map changes](https://github.com/rubygems/rubygems.org/pull/4396) - the first stage of which was a [migration to `propshaft`](https://github.com/rubygems/rubygems.org/pull/4123), allowing us to avoid Node entirely for our assets and still use and update npm packages for JS. The second stage was creating a separate pull request for the import map changes.
34+
- We’ve now begun implementing changes, [adding an API key stimulus controller](https://github.com/rubygems/rubygems.org/pull/4418) and improving it for ease of developer use.
35+
- If you’re interested in learning more about Stimulus.js and its best practices, more information can be found [here](https://www.betterstimulus.com/) and [here](https://thoughtbot.com/blog/taking-the-most-out-of-stimulus).
36+
37+
**Improving the Design of RubyGems Gems page**
38+
- The [Gems page](https://rubygems.org/gems) on RubyGems ranks as the most visited page of the website, serving as a key resource for engineers to understand essential details about a gem, including its purpose, licenses, dependencies, and how to access and install the gem itself. Recognizing the importance of these pages in helping visiting engineers accomplish their tasks, it's crucial to closely examine their needs and ensure that the page structure and design align with their objectives.
39+
- Through interviews and discussions with RubyGems power users and stakeholders, we have been able to identify the fundamental values of the interface elements, understand the reasons behind their development, track their evolution, and determine the most beneficial next steps for our broader user base. Moving forward, we are exploring new design options to enhance user experience on these pages.
40+
41+
**[Initiating the Gem Research Tool Project](https://blog.segiddins.me/2024/02/09/residency-update/)**
42+
- This will be most relevant for RubyGems developers. The team will be able to use this as a playground for features that we want to expose to the public eventually, like browsing gem contents and being able to make queries. We also have been able to use this for security research to assess the impact of particular changes across the entire published gem ecosystem.
43+
- The creation of this tool has involved (and will continue to involve) [a lot of investigation](https://blog.segiddins.me/2024/02/09/residency-update/), experimentation and steps like renting a dedicated server from Hetzner to host the gem research tool, after repeatedly running out of disk space!
44+
45+
**Developing a Pure Ruby Sigstore Implementation**
46+
47+
- This project kicked off with a long-term goal of integrating it directly into RubyGems. The team is drawing inspiration from the existing sigstore and The Update Framework (TUF) implementations in Python.
48+
- We intend to focus on meeting the sigstore compliance specifications through continuous iterations. Additionally, by analyzing code and branch coverage, we're identifying sections that need more extensive testing.
49+
- A critical part of this project is creating a `protobuf` implementation that does not depend on native extensions, ensuring it can be seamlessly incorporated into RubyGems.
50+
51+
In February, RubyGems.org gained [86 new commits](https://github.com/rubygems/rubygems.org/compare/master@%7B2024-2-01%7D...master@%7B2024-2-31%7D) contributed by 13 authors. There were 5,265 additions and 2,022 deletions across 270 files.
52+
53+
## Thank you
54+
55+
Thank you to all the contributors of RubyGems and RubyGems.org for this month! Your contributions are greatly appreciated, and we are grateful for your support.
56+
57+
### Contributors to RubyGems:
58+
59+
- [@nobu](https://github.com/nobu) Nobuyoshi Nakada
60+
- [@martinemde](https://github.com/martinemde) Martin Emde
61+
- [@deivid-rodriguez](https://github.com/deivid-rodriguez) David Rodríguez
62+
- [@VitaliySerov](https://github.com/VitaliySerov) Vitaliy Serov
63+
- [@flavorjones](https://github.com/flavorjones) Mike Dalessio
64+
- [@jgarber623](https://github.com/jgarber623) Jason Garber
65+
- [@kimesf](https://github.com/kimesf) Kim Emmanuel
66+
- [@hsbt](https://github.com/hsbt) Hiroshi Shibata
67+
- [@ccutrer](https://github.com/ccutrer) Cody Cutrer
68+
- [@simi](https://github.com/simi) Josef Šimánek
69+
- [@mame](https://github.com/mame) Yusuke Endoh
70+
- [@segiddins](https://github.com/segiddins) Samuel Giddins
71+
- [@dduugg](https://github.com/dduugg) Douglas Eichelberger
72+
- [@indirect](https://github.com/indirect) André Arko
73+
74+
75+
### Contributors to RubyGems.org:
76+
77+
- [@jenshenny](https://github.com/jenshenny) Jenny Shen
78+
- [@martinemde](https://github.com/martinemde) Martin Emde
79+
- [@segiddins](https://github.com/segiddins) Samuel Giddins
80+
- [@hsbt](https://github.com/hsbt) Hiroshi Shibata
81+
- [@simi](https://github.com/simi) Josef Šimánek
82+
- [@colby-swandale](https://github.com/colby-swandale) Colby Swandale
83+
- [@sh0n0](https://github.com/sh0n0) sh0n0
84+
- [@coorasse](https://github.com/coorasse) Alessandro Rodi
85+
- [@CuddlyBunion341](https://github.com/CuddlyBunion341) Daniel Bengl
86+
- [@albertchae](https://github.com/albertchae) Albert Chae
87+
- [@bradly](https://github.com/bradly) Bradly Feeley
88+
- [@ekyburz](https://github.com/ekyburz) EtienneKyburz
89+
- [@indirect](https://github.com/indirect) André Arko
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

Comments
 (0)