June 2022 Monthly Update
ruby together news
In June, Ruby Together was supported by 32 different companies, including Ruby member Zendesk. 1 company joined as a new member.
On top of that, 1 new developer signed up as a member. In total, we were supported by 127 developer members. Thanks to all of our members for making everything that we do possible. <3
The following is a non-exhaustive list of other improvements included in the above releases (see the changelog for further information):
- fixed a regression when loading old marshaled specs - #5610.
- improved performance of installing gems from gem server sources - #5614.
- fixed incorrect password redaction when there’s an error in
gem source -a- #5623.
- fixed some errors being printed twice in
--verbosemode - #5654.
- created documentation on how to run
rake setupas a regular user - #5662.
- added clear and descriptive messages when
gem updatefails to update some gems - #5676.
In June, RubyGems gained 168 new commits, contributed by 13 authors. There were 1,610 additions and 1,233 deletions across 165 files.
In June, RubyGems.org saw several bug fixes and updates, some of which include the following:
- fixed confusion in MFA behaviour - #3079.
- added a prompt to notify users leaving without copying MFA recovery codes - #3082.
- removed API key
rubygems_idfrom the form url query string - #3085.
- separated MFA methods from
User.rbto its own concern
- added case insensitive uniqueness validation to user handles - #3120.
- added a per user rate limit to the
gem pushcommand - #3121.
- added a Capybara find method to wait for page to load when running tests - #3124.
This month, RubyGems.org gained 74 new commits, contributed by 13 authors. There were 1,015 additions and 263 deletions across 63 files.
As always, we continue to fix bugs, review and merge PR’s and reply to support tickets.
In June we completed 36.4 hours of development work @$150/hour, and spent $ 5,461.50.
Until next time,
Irene, André, and the Ruby Together team
July 22, 2022