Depfu VS Smaller

Depfu mentions (4)

• The what and why of CI

  For everyone that has read my article about the demonstration of security flaws already knows how bad things can turn out, because a library has issues. If I would need to summarize this topic into one word: Log4Shell. The problem with 3rd party software is: When they mess up (security wise), your software can be affected. Luckily, often times libraries give their best to fix those exploits as quickly as... - Source: dev.to / over 1 year ago

• Rubocop Ruby Matrix Gems

  Compounding factor #4: Dependency greening tools, like GitHub's dependabot, or the excellent alternatives depfu, and renovate will all send a PR whenever a new version of rubocop comes out, asking to upgrade from ancient to hot-right-now. While this is often a non-starter for a library, the repeated invalid PRs can be a time sink, and a distraction. - Source: dev.to / about 2 years ago

• Best practice: should I specify versions in Gem file?

  In terms of triggering upgrades, we have depfu/dependabot monitoring our dependencies for us. (Adopted depfu first, but dependabot is now baked into Github.) Its then a case of:. Source: about 2 years ago

• Use depfu and Mergify to automatically merge dependency updates

  For some time, I have updated the projects manually, however this became way too time consuming. Enter depfu, a free (for open source projects) service that keeps your project's dependencies up-to-date by proposing pull requests (PRs) whenever there's a new dependency version. Renovate is a similar service, and would work the same for the purpose of this tutorial. Depfu has made my life much easier – it... - Source: dev.to / about 3 years ago

Smaller mentions (0)