Package groups

Depfu can update packages in groups if they are related and updates are published in lockstep and with identical version numbers. We maintain a public repository on GitHub that accepts pull requests.

The assumption for this repository and the lists published there is that these are all public packages.

Currently grouping only works for Bundler/Rubygems and npm based package managers.

Private package groups

If you want to be able to use these grouped updates for your private packages, you need to define these package groups in the .depfu.yml  config file. Here's a quick example of a config file:

npm:
  package_groups:
    ppg:
    - "@depfutest/ppg-one"
    - "@depfutest/ppg-two"
    - "@depfutest/ppg-three"

Package groups have a label or name (ppg:) and a list of package names. The group name should refer to the main package of a package group for Rubygems but has less meaning in the context of npm packages - It does appear in PR titles, branch names etc., though.

As with the public package groups, the prerequisite for this to work is that all packages are published at the same time and have identical version numbers.