Tips to prepare for dependencies API being deprecated with old ruby

73 views
Skip to first unread message

Owen Urkov

unread,
Apr 5, 2023, 8:21:52 PM4/5/23
to rubygems.org

Hello,

 

We are currently trying to prepare ourselves for the deprecation of the dependencies API as outlined here:
https://blog.rubygems.org/2023/02/22/dependency-api-deprecation.html

We are currently stuck using old versions of Ruby (2.5.0) and Puppet (3.8.7) and fear that our production will come to a halt once the API has been deprecated for good.  Is there any advice folks at rubygems.org could give us to ensure things continue to work as expected Monday?  We currently use bundler to install gem dependencies for Ruby and Puppet modules.  Those projects install gems via artifactory which in turn proxy to rubygems.org.  Any tips would be much appreciated!

 

Thanks in advance,

Owen

Wes Garrison

unread,
Apr 5, 2023, 8:34:30 PM4/5/23
to rubyge...@googlegroups.com
What impact will this deprecation have?
We expect this deprecation to have no user-facing impact.
If you are installing gems from RubyGems.org using versions of Bundler more than 7 years old (1.11 or older), your installs will get slower. Hopefully, everyone has upgraded their copy of Bundler at least once in the last 7 years, and their installs can continue at full speed.

Check your bundler version and make sure it is newer than 1.11 and you should be good to go. 
  
---
Wes Garrison



--
You received this message because you are subscribed to the Google Groups "rubygems.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubygems-org...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubygems-org/d8b081e0-253c-4c8d-ae3b-ca4d18b3d0a6n%40googlegroups.com.

Robert Fletcher

unread,
Apr 6, 2023, 1:51:11 PM4/6/23
to rubyge...@googlegroups.com
I've got an ancient Ruby 1.8.7 project. It's not used by anybody, but I had some hope of tinkering with it and eventually upgrading it at some point. Losing the legacy API seems like it closes off one major avenue to accomplishing this. Any advice on how to make sure I can still work on this project down the road?

Reply all
Reply to author
Forward
0 new messages