Closed stephaniewang526 closed 4 years ago
I think we would need the logs to investigate. 🤔
Maybe this is related to the other maven repo issues we have
Using https://github.com/googleapis/java-translate/pull/344 as an example, we can hopefully fork, clone and check out https://github.com/googleapis/java-translate/commit/97fbd5c45663cf0eb6df4e8d3d1eae4b92efcbb9 and see if it reproduces.
In forked repo, problem is not reproduced as PR is created: https://github.com/renovate-tests/java-translate/pull/8
Turns out our backend thinks this repo disabled:
I have manually flipped it to enabled and a new job ran and created PRs. I will monitor that it doesn't flip itself back to disabled again.
Also, I noticed other googleapis repos were in a similar state (installed but disabled) so I've reset them all so that they get enqueued in the next hourly scheduled runs.
Thank you for looking into this!
We had to make below manual updates ourselves since renovate-bot did not propose these updates:
googleapis/java-webrisk#277 googleapis/java-translate#344
com.google.cloud:google-cloud-shared-dependencies
v0.14.1
andv0.15.0
were both missed in the above two repos. However, we did get renovate-bot updates in our other 70+ Google-provided repos.Could you investigate and let us know why the bot did not work?
Thank you! (related to point 4 in this comment)
cc @chingor