We’ve launched a new dashboard that gives you a detailed overview of your dependencies and their status in Depfu.
Debugging a memory usage problem in our system lead to some interesting insights and some bugfixes for Bundler.
Bundler 2.0 will create lock files that are not backwards compatible. Let's see why these changes have been introduced and what this means for users and tool makers.
We launched special handling of security updates - You'll get them earlier and with additional information on the vulnerabilities.
Bundler 2.0 will change the filename of the Gemfile and Gemfile.lock. Let's look at why that is and what this means for you (and us).
Since a lot of people asked about it, Depfu will no longer update gems when the new version is outside of your version constraints by default.
A look at the many ways you can tell Bundler how to access private dependencies.
We changed how and when Depfu runs dependency updates on your repo to minimize the impact on your CI service.
Let's see how Bundler's new command line options allow you to be more conservative when updating gems.
We take modern dependency management solutions for granted these days, but how did it all start? What are the most important ideas and when and where were they introduced?
We believe doing small, easy to assess updates regularly and supported by automation is the best way for busy teams to keep their apps up-to-date.
Get your app up-to-date →