shollyman

This commit **initializes a new release** for the **`bigquery` client library**, advancing its version from `v1.74.0` to `v1.75.0`. As a **maintenance** task, it updates the internal `Version` constant within `bigquery/internal/version.go` and modifies the `.librarian/state.yaml` configuration to reflect the new version. Additionally, a minor fix corrects the Apache license URL in the `version.go` file header. This automated preparation by the Librarian CLI sets the stage for the official `bigquery` module release.

This commit **re-enables the automatic generation process for the `auditmanager` module**, restoring a critical automated workflow. As a **maintenance chore**, this action ensures that the `auditmanager` components or related artifacts are consistently updated and correctly integrated. This change primarily impacts the **`auditmanager` subsystem**, ensuring its ongoing development and maintenance benefit from automated tooling.

This commit **updates the golden files** within the `internal/godocfx` module's test suite. It specifically adjusts the expected documentation output for the `cloud.google.com/go/storage@v1.33.0` library, modifying the link format for `Query.StartOffset` and `Query.EndOffset` within the `index.yml` golden file. This **test update** ensures the documentation generation process correctly reflects the desired link structure for these specific fields, preventing future test failures due to format discrepancies. The change was automatically generated using `go test -update-goldens`.

This commit **skips the flaky `TestIntegration_AdminCreateInstance` integration test** within the **Bigtable client library**. This is a **maintenance chore** to improve the reliability of continuous integration pipelines by temporarily disabling a test that frequently fails due to external factors. The change affects only the test suite in `bigtable/integration_test.go`, ensuring that CI runs are more stable while the underlying flakiness issue is investigated.

This commit introduces a **maintenance update** to the **continuous integration (CI) pipeline**, specifically within the `internal/kokoro/continuous.sh` script. It modifies the `runDirectoryTests` function to **always execute `go mod tidy`** for generated code snippets. This change ensures that `go.mod` and `go.sum` files are consistently synchronized with the actual dependencies of generated code, preventing potential build failures or dependency mismatches in the CI environment. This improves the reliability of the **build process** and maintains the integrity of **Go module dependency management** for generated components.

This commit **improves the robustness of Bigtable integration tests** by refining how error messages are asserted. Specifically, the `TestIntegration_Aggregates` function within `bigtable/integration_test.go` now utilizes a **regular expression match** for error message assertions, replacing the previous direct string containment check. This **test maintenance** change makes the integration tests less brittle and more resilient to minor, non-semantic variations in error string formatting. The update ensures that tests remain stable and continue to pass even if error messages are slightly reworded, without impacting the core Bigtable client library's functionality.

This commit **relaxes an assertion** within the **BigQuery client library's integration tests** to improve test stability. Specifically, the `TestIntegration_QueryStatistics` test in `bigquery/integration_test.go` is modified to only fail if the `TotalSlotDuration` metric reports a negative value. This **test maintenance** prevents potential flakiness by allowing non-negative slot durations, ensuring the test accurately reflects expected behavior without being overly restrictive. The change helps maintain a robust CI/CD pipeline by reducing false negatives in the **BigQuery test suite**.

chore: tidy snippets (#14028)

This commit prepares for the **BigQuery module's v1.74.0 release**, which introduces the `TotalServicesSkuSlotMillis` field to `QueryStatistics` for enhanced query metrics. It updates the internal version constant in `bigquery/internal/version.go`, the `.librarian/state.yaml` configuration, and numerous generated snippet metadata files across various BigQuery sub-APIs to reflect this new version. This **maintenance** commit is a **release preparation** step, and merging it will automatically trigger the official release of the updated **BigQuery client library**, making the new feature available to users.

This commit introduces a **new Go client library** for the **Hypercompute Cluster API (v1)**, enabling programmatic interaction with hypercompute cluster resources. It provides a comprehensive **new capability** by adding the `hypercomputecluster/apiv1` module, which includes the core client implementation, auxiliary types for long-running operations, helper functions, and detailed package documentation. The update also incorporates generated example tests and code snippets for various client methods like `CreateCluster`, `ListClusters`, and `DeleteCluster`, facilitating easier adoption and usage for developers. This significantly expands the project's support for managing hypercompute clusters.

This commit performs a **maintenance chore** by updating the **`apidiff` GitHub Actions workflow** to resolve linting issues. Specifically, it modifies the `.github/workflows/apidiff.yml` file to ensure `GITHUB_OUTPUT` assignments are properly quoted. This change improves the robustness and reliability of the **CI/CD process** by preventing warnings or errors related to output variable assignments within the API difference checking pipeline.

This commit performs a significant **infrastructure update** to advance the project's Go version support, officially moving towards **Go 1.26** as the new upper bound and updating the minimum supported version. It primarily affects the **CI/CD pipelines**, with workflows such as `apidiff.yml`, `conformance.yaml`, `third_party_check.yml`, and `vet.yml` now configured to run with Go 1.26. Additionally, **documentation** in `README.md` and `bug_report.md` is updated to reflect the new Go version policy, and the `renovate.json` configuration is adjusted. This **maintenance** effort ensures the project's development environment and automated checks remain compatible with current Go releases, leveraging the latest language features and improvements.

chore: tidy snippets (#13869)

This commit performs **maintenance** by **removing flaky OpenTelemetry tests** from the **Spanner client library**. These unreliable tests were causing instability and hindering monorepo management by generating false-positive failures. Per maintainer guidance, the tests are permanently removed to improve the overall reliability of the test suite and streamline development workflows.

This commit introduces the **new Workload Manager API client library** for Go, providing comprehensive programmatic access to the Workload Manager service. This **new capability** includes the full generated client implementation (`workloadmanager/apiv1/workload_manager_client.go`), auxiliary functions, and a suite of generated code snippets for various API methods such as `CreateEvaluation`, `RunEvaluation`, and `ListExecutions`. The work also encompasses new documentation, metadata, and example tests for the client. This addition enables Go developers to seamlessly integrate with and manage workloads through the Workload Manager API within their applications.

This commit **skips** the `TestIntegration_AdminEncryptionInfo` integration test within the **Bigtable client library**. This **maintenance change** addresses extreme flakiness, which has been causing over 50% of recent nightly test failures. By temporarily disabling this test in `bigtable/integration_test.go`, the project aims to improve the stability and reliability of its **CI/CD pipeline** until the underlying issue can be resolved. This action prevents misleading test results and allows focus on other valid failures, specifically impacting the **Bigtable admin encryption info** test coverage.

This commit is a **maintenance chore** that prepares for the **release of version 0.18.2 of the `auth` module**. It specifically incorporates a **bug fix** addressing issues with GDCH credentials logic. The changes involve updating the internal version constant within `auth/internal/version.go` and modifying the librarian state configuration in `.librarian/state.yaml` to reflect the new version. This ensures that the `auth` module provides improved stability and correct behavior for users relying on GDCH credentials.

This commit performs **maintenance** to **complete the initial generation** of the **Data Manager API client library**, addressing files that were inadvertently omitted during previous regeneration efforts. It introduces a comprehensive `README.md` to the `datamanager` module, providing an overview, installation instructions, and stability information. Additionally, it adds `version.go` files to both the `datamanager/apiv1` and `datamanager/internal` packages, establishing and initializing the client's tagged release version. This work ensures the **Data Manager API client library** is fully documented and properly versioned from its inception.

This commit provides a **maintenance fix** for the **Spanner client library's OpenTelemetry integration tests**. It resolves a **build failure** in `TestSpannerTracesWithOpenTelemetry` by updating a **deprecated call signature** within the `otelgrpc` invocation. Specifically, the change modifies the OpenTelemetry gRPC client configuration in `spanner/test/opentelemetry/test/ot_traces_test.go`, transitioning from using a stream interceptor to a `stats handler`. This ensures the **OpenTelemetry tracing tests for Spanner remain functional** and continue to provide valid coverage for the integration.

This commit is a **maintenance chore** that **relaxes code ownership rules** for the `internal/generated/snippets` directory. It modifies the `.github/CODEOWNERS` file to remove the previously defined owners for this specific path. This change aims to **reduce friction for maintainers and committers** by streamlining the review and approval process for contributions affecting these generated snippet files.