package dependency where the relationship is _only_ devDependency

[jbolda]

npm has the concept of a devDependency where this list of packages is only installed when you are developing the package (and not when you are installing it via it being required in your list of dependencies). If a relationship is only through a devDep, incrementing the version number in a devDep may not actually change the released assets. If it is a library, it likely won't. If you are using a devDep to build assets into a dist directory or similar, it may affect the released assets. We currently don't differentiate between dev/devDep, but we may want to give the option in the case of libraries to not bump a parent if it is strictly a devDep that doesn't affect the output release assets.