The bot keeps opening release PRs for already (manually) released versions

[plamut]

A recent BigQuery release PR had some issues with release notes (more here), thus a manual 2.21.0 release PR was created with the desired changes and then merged.

The bot then kept opening 2.21.0 release PRs, not realizing that a release has already been made. We eventually merged one of those PRs which was effectively a no-op to solve the problem.

If it helps, I'm providing a link to all BigQuery 2.21.0 release PRs to investigate:
https://github.com/googleapis/python-bigquery/pulls?q=is%3Apr+is%3Aclosed+%22chore%3A+release+2.21.0%22+sort%3Aupdated-desc+

[live627]

I'm going to go out on ca climb here and say that the version could be bumped via a commit.

[bcoe]

@plamut the branch naming used by release-please is what's used to find prior releases, and create the appropriate release PR. There's not an easy way today to override this behavior.

[chingor13]

This should have been fixed in #1267 available in 13.4.8