Cody Oss

This commit **fixes a bug** in the **changelog generation process** by adding a previously missing heading. This **maintenance change** specifically addresses an issue that was preventing the correct creation of **release pull requests**. By ensuring the changelog is properly formatted, the automated release workflow for the project can now proceed without errors.

This commit **integrates Vertex AI** into the project's existing **automation infrastructure**, enabling automated processes to manage or interact with Vertex AI services. It performs the necessary **onboarding steps** to ensure Vertex AI is properly configured for automated workflows. This **maintenance chore** enhances internal tooling and sets the foundation for more efficient development and deployment workflows involving Vertex AI. The change primarily impacts the **internal automation system** and the programmatic management of **Vertex AI resources**.

This commit performs a **multi-module release**, updating several Google Cloud Go client libraries to their latest versions. It introduces **new features** across **AI Platform**, **Dataplex**, **Document AI**, **IAP**, **Security Command Center**, **Shopping**, and **Vector Search**, alongside a **bug fix** for **Audit Manager**. Notable additions include `embed_content_config` and `VALIDATED` Function Calling mode for AI Platform, `DataProductService` and `OneTime` triggers for Dataplex, and marking Vector Search v1 API as GA. This **maintenance** release ensures users have access to the latest API capabilities and fixes by bumping version constants and updating snippet metadata files across the affected modules.

This commit introduces a **maintenance fix** to the **`librarian` configuration** for the `sqlalchemy-bigquery` library. It resolves an issue where the `librarian` tool was failing to correctly identify the library's tag by adding the necessary `tag_format` setting to the `.librarian/state.yaml` file. This ensures proper dependency management and prevents potential build failures related to `sqlalchemy-bigquery` within the system. The change specifically targets the **dependency resolution mechanism** handled by `librarian`.

This commit **fixes a bug** in the **`compute/metadata` package** by ensuring the `subClient` field is correctly initialized within the `NewWithOptions` function when the `UseDefaultClient` option is enabled. Previously, this field might have been left unset, leading to potential runtime issues or incorrect behavior when the metadata client was configured to use the default underlying client. A new **test case** has been added to `metadata_test.go` to validate this fix and prevent future regressions, thereby **improving the robustness** of the metadata client's initialization.

This commit implements a **bug fix** within the **`compute/metadata`** package to address issues with client timeouts. It modifies the `newDefaultHTTPClient` function to **conditionally disable HTTP client timeouts**, including idle connection and request timeouts, based on a new `enableTimeouts` parameter. This change is specifically targeted at the **subscription client**, preventing premature disconnections and ensuring more robust and reliable long-lived connections for metadata retrieval.

This commit **fixes a critical bug** in the **`compute/metadata` package** by ensuring the `subClient` field within the `Client` struct is properly initialized during `NewClient` creation. Previously, this field could be uninitialized, potentially leading to **nil pointer dereferences** and runtime errors when interacting with the metadata subscription client. Concurrently, it **improves test reliability** by addressing a racy condition in `TestSubscribeUsesSubscribeClient` and adding assertions for the `subClient` field in client creation tests. These changes enhance the **stability and correctness** of the metadata client and its associated tests.

This commit introduces a **refactoring** and **bug fix** within the **`compute/metadata` package** to enhance the reliability of subscription methods. It configures the default client to use a **separate HTTP client for subscription calls**, specifically designed without an idle timeout to prevent premature connection closure during long periods of inactivity. Additionally, this change **fixes a bug** where `Subscribe` methods, such as `SubscribeWithContext`, were not correctly honoring context errors, improving the robustness of metadata subscriptions. This ensures more stable and predictable behavior for applications relying on long-lived metadata updates.

This commit performs a **maintenance chore** by re-enabling the generation of **audit-related protobuf definitions** within the `genproto` module. It updates `internal/gapicgen/generator/genproto.go` to include `google.golang.org/genproto/googleapis/cloud/audit` in the list of protos to be generated. This ensures that **cloud audit protos** are consistently produced and available in the `genproto` repository, addressing a previous generation omission.

This commit primarily **upgrades the project's Go version support**, updating **CI/CD workflows, build environments, and documentation** to utilize **Go 1.24 and 1.25**, while deprecating Go 1.23. As part of this **maintenance** effort, several modules including **Bigtable and Pub/Sub** receive minor **refactorings** to consistently use `status.Error` instead of `status.Errorf` for gRPC status errors. Various **test files** are also adjusted for compatibility and consistency, such as updating loop iteration styles and error creation methods. This ensures the project leverages the latest Go features and remains compatible with current development standards across its **tooling and core libraries**.

This commit delivers a **bug fix** addressing a **nil pointer exception** within the `internal/godocfx/pkgload` module. The error arose when `package.Load` encountered untidied modules, returning an invalid package entry like `'cloud.google.com/go/foo/...'` that was erroneously used for module path detection. To resolve this, the `load.go` file was refactored, introducing a new helper function `getModulePath` to correctly filter out such invalid entries. This ensures more robust module detection for `godocfx`, improving the reliability of package loading even when `go.mod` tidy errors are present, and is verified by new tests in `load_test.go`.

This commit introduces a **bug fix** to the **`internal/godocfx` tool** to improve its handling of Go modules, especially v2 versions. It **adds sorting logic** to the `pkgload.Load` function, ensuring that v1 modules are processed before v2 modules based on their package paths. This crucial change **prevents a panic** that previously filtered away all results, thereby enhancing the tool's stability and correctness. Additionally, the module `'cloud.google.com/go/spanner/benchmarks'` has been added to the module skiplist in `main.go` as part of this **maintenance** effort.

This commit performs **code style maintenance** to resolve **goimports formatting errors** within the `internal/librariangen` module. Specifically, it reformats test case struct fields in `execv_test.go` and adjusts indentation and removes blank lines in `release.go` and `release_test.go`. These changes ensure consistency with standard Go formatting, thereby improving the **readability and maintainability** of these internal components. The fix is confined to the `librariangen` internal tooling and has no direct impact on external functionality or user-facing features.

This commit performs essential **infrastructure setup** to **onboard new shopping clients** by configuring automated code generation and processing. It updates the **OwlBot configuration** in `.github/.OwlBot.yaml` to include new **shopping merchant API paths**, enabling automated code generation and removal for these services. Concurrently, the **internal postprocessor configuration** in `internal/postprocessor/config.yaml` is modified to define these new **shopping merchant API services**, specifying their input directories and import paths. This **maintenance** work ensures the system is prepared to handle and process new shopping-related APIs effectively.

This commit performs **maintenance** to **onboard** the **BigQuery Data Policies v2beta1 API** by updating core infrastructure configurations. It adds new configuration entries to `.github/.OwlBot.yaml` to ensure OwlBot correctly handles the new API paths. Concurrently, `internal/postprocessor/config.yaml` is updated to include a service configuration for the `v2beta1` version of the BigQuery Data Policies. This work **prepares the project's internal tooling and infrastructure** to support the new API, enabling future code generation and processing for this specific BigQuery feature.

This commit performs a **chore** to **onboard the `schemaregistry v1` API for the Managed Kafka service**. It updates internal tooling configurations to properly support this new API version. Specifically, new deep-remove and deep-copy rules are added to the `.github/.OwlBot.yaml` configuration, alongside a new service entry in `internal/postprocessor/config.yaml`. This foundational **maintenance** work ensures automated handling and processing are correctly set up for the `managedkafka schemaregistry v1` API.

This commit performs **maintenance** by updating internal configurations to support **new API versions (v1 and v1alpha) for various shopping merchant services**. It modifies the **OwlBot configuration** in `.github/.OwlBot.yaml` to correctly handle these new versions for deep-remove and deep-copy operations, ensuring proper code generation and synchronization. Concurrently, the `internal/postprocessor/config.yaml` is updated to include the necessary service configurations for these new API versions. This work ensures the system is prepared to integrate and process data from the latest iterations of the shopping merchant APIs.

This commit performs a **chore** to onboard the new `apiv1beta` and `apiv1` versions of the **configdelivery** module. It updates the `.OwlBot.yaml` configuration to ensure these API versions are properly handled for deep removal and copying within the repository. Additionally, the `internal/postprocessor/config.yaml` is modified to include these new service configurations for internal post-processing. This **maintenance** task ensures the project's build and release pipelines correctly recognize and manage the latest `configdelivery` API specifications.

This commit **onboards** the `licensemanager/apiv1` module into the project's automated tooling infrastructure. This **chore** updates the **OwlBot configuration** (`.github/.OwlBot.yaml`) to include `licensemanager/apiv1` paths for automated code synchronization. Additionally, it modifies the **postprocessor configuration** (`internal/postprocessor/config.yaml`) to enable processing for the `licensemanager` module. This integration ensures that the new API version is properly managed by existing automation, streamlining its development and maintenance.

This commit performs a **maintenance chore** by updating the digest for the **OwlBot Docker image** within the `.github/.OwlBot.lock.yaml` file. This action ensures that the automated postprocessing steps executed by **OwlBot** in the **CI/CD pipeline** leverage the most current and stable version of the tool. The update helps maintain the integrity and currency of the build and release process, without introducing any changes to the application's core functionality.