versions in README.md seems lagged

[zhumin8]

According to versions.txt, last released version of google-cloud-accessapproval is 2.93.0

google-cloud-java/versions.txt

Lines 5 to 8 in d809a40

	google-cloud-accessapproval:2.93.0:2.94.0-SNAPSHOT
	grpc-google-cloud-accessapproval-v1:2.93.0:2.94.0-SNAPSHOT
	proto-google-cloud-accessapproval-v1:2.93.0:2.94.0-SNAPSHOT
	google-identity-accesscontextmanager:1.93.0:1.94.0-SNAPSHOT

Current version from pom.xml matches

google-cloud-java/java-accessapproval/pom.xml

Line 7 in d809a40

<version>2.94.0-SNAPSHOT</version><!-- {x-version-update:google-cloud-accessapproval:current} -->

However README.md is pointing to 2.92.0

google-cloud-java/java-accessapproval/README.md

Lines 41 to 46 in d809a40

	```xml
	<dependency>
	<groupId>com.google.cloud</groupId>
	<artifactId>google-cloud-accessapproval</artifactId>
	<version>2.92.0</version>
	</dependency>

This issue looks like consistent for a few other libraries I spot checked.

[zhumin8]

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]

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?

[blakeli0]

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?

The daily generation seems to be failing after May 5, I just manually triggered a new one and see if makes any differences.

[blakeli0]

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]

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]

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.