In google-cloud-node, every time we merge a release PR it updates the global changelog which creates a merge conflict for every other release PR.
https://screenshot.googleplex.com/5af6nAnWquSjuSZ
This can be resolved by re-running release-please (with the force run label), but when we have a large number of releases this can be very tedious (it needs to be repeated for each subsequent release).
I think we wouldn't have this difficulty any more if we moved to a per-library changelog.
In google-cloud-node, every time we merge a release PR it updates the global changelog which creates a merge conflict for every other release PR.
https://screenshot.googleplex.com/5af6nAnWquSjuSZ
This can be resolved by re-running release-please (with the force run label), but when we have a large number of releases this can be very tedious (it needs to be repeated for each subsequent release).
I think we wouldn't have this difficulty any more if we moved to a per-library changelog.