Developers must update their code to accommodate several breaking changes. The name and parent parameters are now strictly required for certain methods; ensure these are always provided. Specifically, name for checkFeaturePolicyMembers and parent for batchUpdate, list, and update on UserAvailabilities are now mandatory. Additionally, the verification property in GoogleCloudDiscoveryengineV1EngineFeaturePolicyMember (and its alpha/beta variants) and the updateTime property in GoogleCloudDiscoveryengineV1alphaUserAvailability are now read-only. Any attempts to write to these fields will now fail.
On the feature front, new methods are available for UserAvailability resources: projects.locations.userStores.userAvailabilities.batchUpdate, projects.locations.userStores.userAvailabilities.list, and projects.locations.userStores.userAvailability.update. These enable programmatic management of user availability states. A new projects.locations.collections.engines.checkFeaturePolicyMembers method has also been added, allowing developers to pre-validate engine feature policy members against the project's directory before saving, helping prevent configuration errors.
