fix: remove variant_retrievable_fields and materials fields from the product.proto
fix: minor API doc change on removing the '>' sign escaping.
PiperOrigin-RevId: 339939234
BREAKING CHANGE: update package names to avoid conflict with google-cloud-bigquery
The google-cloud-bigquery package uses the `google.cloud.bigquery` path as a
plain Python module, not a namespace package. When this package and
google-cloud-bigquery are installed in the same environment, conflicts can
result.
PiperOrigin-RevId: 339531446
BREAKING CHANGE: update package names to avoid conflict with google-cloud-bigquery
The google-cloud-bigquery package uses the `google.cloud.bigquery` path as a
plain Python module, not a namespace package. When this package and
google-cloud-bigquery are installed in the same environment, conflicts can
result.
PiperOrigin-RevId: 339505822
This allows each (API,version,language) combination to provide a
mapping between RPCs and library methods invoking those RPCs.
PiperOrigin-RevId: 339325081
feat: Added API service description
fix!: Renamed ProductLevelConfig enum names in CatalogService
BREAKING CHANGE: the renaming is a breaking change but since the API is not used anywhere and client libraries generation has not started, it's a safe change.
fix: a few minor API doc changes.
PiperOrigin-RevId: 339268186
BREAKING CHANGE: update package names to avoid conflict with google-cloud-bigquery
The google-cloud-bigquery package uses the `google.cloud.bigquery` path as a
plain Python module, not a namespace package. When this package and
google-cloud-bigquery are installed in the same environment, conflicts can
result.
PiperOrigin-RevId: 339048690
Changes include:
- bazel: utilize WKT for some Go deps
- gapic: add `module` plugin option - not for bazel
- updated Go & bazel dependencies
PiperOrigin-RevId: 337404700
fix!: Use the common Location resource name.
BREAKING CHANGE: rename stocking_unit_retrievable_fields to variant_retrievable_fields in Product.proto. Since the API is still under development and not yet launched and the client library generation is not started, this change should be safe.
BREAKING_CHNAGE: remove event_source field in the user_event.proto. API is not used anywhere so it's safe.
PiperOrigin-RevId: 337386065
- Fix a scenario where generator attempts to assign a string to an integer in tests by using a separate value generator in test generation
PiperOrigin-RevId: 336931287
