librarian: bulk changes reports the same libraries multiple times #2690
Description
I'm trying to migrate errorreporting for google-cloud-go - this is unusual as it hasn't been regenerated in two years. I thought I'd see what happened if I regenerated, then simulated a release.
The release notes look okay until we get to the bulk changes, where there are three entries like this:
* fix: update golang.org/x/net to 0.37.0 ([11449782](https://github.com/jskeet/google-cloud-go/commit/11449782))
Libraries: errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting,errorreporting
(Each entry has a different message, but errorreporting is listed many times in each entry.)
My guess is this is a bug with the bulk change checker. There may well be something odd in the repo history that provokes this, but should we ever list the same library multiple times in a single entry?
Metadata
Metadata
Assignees
Labels
No labels