Incorrect bump notes added when --scope is used #1033
Description
When running beachball with --scope, it correctly only releases those packages and does not bump any dependents, but it still adds change notes that describe those bumps as if those dependents were bumped.
Context: We're using beachball 2.51.0 in a monorepo of loosely related npm packages, where the packages depend on each other but they use broad semver ranges like ^6. We don't want beachball to automatically bump or change these semver expressions.
What we observed:
We ran a release job with CI that ran beachball publish --yes --no-push --verbose --scope=@org/foo.
(Not sure if this matters, but the CI script also ran beachball sync --scope @org/foo before that).
At that time, the only change note was for @org/foo with a minor bump.
The @org/foo package depends on another package called @org/utils which lives in the same monorepo. It depended on it using a semver range of "^6".
At the time of release, @org/utils had an actual version of 6.21.1.
After the release, we saw that: in addition to releasing @org/foo as expected, and adding that change note to its changelog(s), it also added another change that said Bump @org/utils to v6.21.1. However, @org/foo's package.json dependency expression remained the same: "@org/utils": "^6".
So there seems to be some discrepancy between --scope and the fact that it doesn't bump dependent packages, and what it writes to the changelogs. It looks like it generates change notes for what would have happened if --scope was not passed.
If you need a repro, please give an example repro that I can copy and modify, or please document the preferred way to create a repro. I didn't find any info in CONTRIBUTING.md.