^{Originally posted by jcageman November 11, 2024}

Using central package management together with libraries that are versioned. When using

{
  "extends": [
    "config:recommended"
  ],
  "bumpVersion": "patch"
}

i expect version bumps on dependencies in central package management to also update the project version when there are changes.

Repro:
https://github.com/jcageman/renovate_repro_bumpversion

See also relevant PR example: https://github.com/jcageman/renovate_repro_bumpversion/pull/1/files#diff-4d59c677ea4c9112e0ce2f2e527693f48dcbcf66ba4eeb4b01abb5f3da8bbe11

Maintainer note

Today bumpVersion only works when the package file version exists in the same file as where the dependency is being updated. To achieve the above means a refactoring of generic bumpVersion logic so that it can return a different modified file to the one already modified by the dependency bump.

Reproduction forked to https://github.com/renovate-reproductions/32452