A dependent that bundles a sibling only ever gets a patch from the sibling's release #80

When a package releases, a dependent whose only change is the dependency bump is forced to a patch release. That is right for a dependent that installs the sibling, but not for one that bundles it: ExaDev/process-graph publishes one package, process-graph, which inlines its private workspace packages and lists them in devDependencies (ExaDev/process-graph#41). A feat commit confined to a private package's directory releases that package at a minor version and process-graph at a patch, although the new feature ships in process-graph's bundle.

The forced-patch logic in the scoped analyzer (createScopedPlugins, the No releasable commits under ..., forcing a patch release path) has no way to carry the dependency's release type to the dependent.