`lerna changed` assumes all packages are changed (non-independent versioning)

[jmuzina]

All of our packages are being published on publishing workflows, even if they were not directly or indirectly updated.

Current Behavior

lerna changed, which is used under the hood by lerna version and lerna publish, is outputting all packages as changed even when run just after a publishing action.

➜  ds25 git:(main) bun run lerna changed
$ lerna changed
lerna info Assuming all packages changed
@canonical/biome-config
@canonical/typescript-config-base
@canonical/typescript-config-react
@canonical/ds-react-core
@canonical/styles
@canonical/utils

Expected behavior

• lerna changed should only output packages that have been updated since the last publishing action. Lerna should read the local git context and determine which packages were changed by comparing against published packages.
• lerna version and lerna publish should only version packages that were updated (directly or indirectly)

[jmuzina]

Possibly related: https://github.com/lerna/lerna/issues/1357 This behavior seems to deviate from what is suggested in Lerna's docs ("Lerna will only version and publish packages that have changed since the previous release")