chore(main): release 1.85.0

[diegomarquezp]

🤖 I have created a release beep boop

1.85.0

1.85.0 (2026-04-14)

Features

• [appoptimize] new module for appoptimize (#12768) (050187d)
• [chronicle] Add DataTableService to Chronicle v1 Client Libraries (fc62b1e)
• [databasecenter] Add support for BigQuery datasets and (fc62b1e)
• [dataplex] Allow Data Documentation DataScans to support BigQuery (fc62b1e)
• [dataproc] Add Engine field to support LightningEngine in (fc62b1e)
• [discoveryengine] add AUTO condition to SearchAsYouTypeSpec in (fc62b1e)
• [infra-manager] adding DeploymentGroups, you can now manage (fc62b1e)
• [kms] add a variable to SingleTenantHsmInstanceCreate to control (fc62b1e)
• [kms] support external-μ in the Digest (fc62b1e)
• [shopping-merchant-products] a new field base64_encoded_name is (fc62b1e)
• [vectorsearch] Added CMEK support (fc62b1e)

Bug Fixes

• auth: Address ClientSideCredentialAccessBoundary RefreshTask race condition (#12681) (30088d2)
• bqjdbc: lazily instantiate Statement in BigQueryDatabaseMetaData (#12752) (72e5508)
• deps: update the Java code generator (gapic-generator-java) to (fc62b1e)
• gdch: support EC private keys (#1896) (bf926fb)
• update appoptimize version to 0.0.1 to match released repo (#12782) (80dfac6)

Documentation

• [network-management] Update comment for the region field in (fc62b1e)
• [shopping-merchant-inventories] A comment for field name in (fc62b1e)

---

This PR was generated with Release Please. See documentation.

[gemini-code-assist]

Code Review

This pull request transitions the repository from snapshot to release versions, specifically updating the project to version 1.85.0. The changes encompass updates to the release manifest, changelog, workspace settings, and version strings across numerous POM files and internal Java classes. Feedback focused on correcting metadata keys in versioning comments within the accesscontextmanager module to ensure consistent and accurate automated version tracking.

[gemini-code-assist]

The version update comment for the parent project is inconsistent with other modules in this repository. It should use the main library key google-identity-accesscontextmanager:current instead of the proto-specific key proto-google-identity-accesscontextmanager-v1:current to ensure consistent automated versioning across the module.

Suggested change

	<artifactId>google-identity-accesscontextmanager-parent</artifactId>
	<version>1.92.0</version><!-- {x-version-update:google-identity-accesscontextmanager:current} -->

[gemini-code-assist]

The version update comment for the proto-google-identity-accesscontextmanager-type dependency is incorrect. It should use the key proto-google-identity-accesscontextmanager-type:current to correctly track the version of the dependent artifact, rather than reusing the key for the current module.

Suggested change

	<version>1.92.0</version><!-- {x-version-update:proto-google-identity-accesscontextmanager-v1:current} -->
	<version>1.92.0</version><!-- {x-version-update:proto-google-identity-accesscontextmanager-type:current} -->