You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed this while testing librarian migrate. IREADME.md files are generated by owlbot.py according to versions.txt in hermetic build.
So I suppose this version difference can happen when google-cloud-java created a new release, but not generated according to the new versions. (daily generation workflow PR is not merged in).
I believe the version difference observed is reasonable given there has not been generation PR merged after release?
But these 2 things seems suspicious to me:
chore: Update generation configuration at Tue May 5 19:42:41 UTC 2026 #13014 generation brought no code change other than googleapis commitish, contradicts with description. Briefly looked at log, generation seems to succeeded with no issues and a v1beta1/ReasoningEngineRuntimeRevisionServiceClient.java is added. This java class is not present in codebase main branch.
I expect daily generation PRs. But there is no open generation PRs and I don't see closed ones after May 05. Am I missing anything?
@blakeli0@jinseopkim0 If I am missing any context or there are on-going issue with generation process?
Thanks, I see #13168, but failing ci at compile. Suspect it has to do with partial release steps (#13168 (comment)), I closed PR and triggered workflow again.
Separately, it's worth noting that a few libraries' libraries-bom version in README has not been updated in a few months. See #13058.
Hmm, since we are still using owlbot.py for README generation, I expect this issue should still persist with librarian. Proved in my local migrate test, librarian generate bigtable did not produced diff in README.
Activity
zhumin8 commentedon May 11, 2026
I noticed this while testing librarian migrate. IREADME.md files are generated by owlbot.py according to versions.txt in hermetic build.
So I suppose this version difference can happen when google-cloud-java created a new release, but not generated according to the new versions. (daily generation workflow PR is not merged in).
The latest release is https://github.com/googleapis/google-cloud-java/releases/tag/v1.86.0 May.05, and no open generation PR.
Last PR merged in before release: #13014
zhumin8 commentedon May 11, 2026
I believe the version difference observed is reasonable given there has not been generation PR merged after release?
But these 2 things seems suspicious to me:
v1beta1/ReasoningEngineRuntimeRevisionServiceClient.javais added. This java class is not present in codebase main branch.@blakeli0 @jinseopkim0 If I am missing any context or there are on-going issue with generation process?
blakeli0 commentedon May 11, 2026
The daily generation seems to be failing after May 5, I just manually triggered a new one and see if makes any differences.
blakeli0 commentedon May 11, 2026
Separately, it's worth noting that a few libraries' libraries-bom version in README has not been updated in a few months. See #13058.
zhumin8 commentedon May 12, 2026
Thanks, I see #13168, but failing ci at compile. Suspect it has to do with partial release steps (#13168 (comment)), I closed PR and triggered workflow again.
zhumin8 commentedon May 12, 2026
Hmm, since we are still using owlbot.py for README generation, I expect this issue should still persist with librarian. Proved in my local migrate test,
librarian generate bigtabledid not produced diff in README.zhumin8 commentedon May 14, 2026
fixed in #13188