After every PR merge on github repo release-please bot is trying to do a release of an already released version.
Example:
Successful release of 2.2.1b2 : googleapis/python-spanner-django#687
still reattempted by bot:
googleapis/python-spanner-django#689
googleapis/python-spanner-django#690
Any idea what is causing this and how to resolve it ?
There is a whole list with 2.2.1b1 https://github.com/googleapis/python-spanner-django/pulls?q=is%3Apr+is%3Aclosed
Is this a client library issue or a product issue?
Not sure, maybe just a client level issue in configuration or maybe a version name mismatch from the django client.
Did someone already solve this?
Do you have a support contract?
Environment details
OS: NA
Node.js version: NA
npm version: NA
release-please version: latest in production
Steps to reproduce
Merge a commit to repo https://github.com/googleapis/python-spanner-django master branch.
Release please bot will create a new release PR similar to this: chore: release 2.2.1b2 Delete LICENSE #690
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!
After every PR merge on github repo release-please bot is trying to do a release of an already released version.
Example:
Successful release of 2.2.1b2 : googleapis/python-spanner-django#687
still reattempted by bot:
googleapis/python-spanner-django#689
googleapis/python-spanner-django#690
Any idea what is causing this and how to resolve it ?
There is a whole list with 2.2.1b1 https://github.com/googleapis/python-spanner-django/pulls?q=is%3Apr+is%3Aclosed
Environment details
release-pleaseversion: latest in productionSteps to reproduce
Making sure to follow these steps will guarantee the quickest resolution possible.
Thanks!