Jon Skeet

This commit introduces a **new capability** to the **`librarian`** system, enabling a "release-only" mode for `legacylibrarian`. It modifies the `handle_release_stage` function in `.generator/cli.py` to conditionally update per-library changelog files. This ensures that during the **migration** to the new `librarian` generation, `legacylibrarian` can still be used for releases (like Docker image bumps) without attempting to update changelogs when no library changes are provided. This prevents errors and allows `legacylibrarian` to operate correctly in a reduced capacity, focusing solely on the release process.

This commit performs a **maintenance update** by bumping the **`area120` client library** to its **experimental release `v0.10.0`**. It updates the library's version in the `.librarian/state.yaml` configuration, the internal `Version` constant within `area120/internal/version.go`, and the client library version specified in the generated snippet metadata for `area120` tables. This ensures all relevant project files reflect the new `0.10.0` release for the `area120` module, making the updated version available for use.

This commit **introduces an experimental `librarian.yaml` configuration file** to the project, intended for defining and managing **Python library settings**. As a **chore**, this addition lays the groundwork for future enhancements in **Python environment configuration** or dependency management. Notably, the file is currently inactive and not being used by the system, as indicated by a prominent notice within its contents. Its scope is limited to preparing for potential future tooling integration without immediate functional impact.

This commit performs a **code reformatting** operation across several Python packages to enhance **code style consistency**. It specifically **reorders import statements** within numerous `.pyi` stub files belonging to the **google-cloud-access-context-manager**, **googleapis-common-protos**, and **grpc-google-iam-v1** libraries. This **maintenance** task, executed using `nox -s format`, ensures uniform formatting and improves readability of type hint definitions. The changes are purely stylistic and do not alter any functional behavior, contributing to better overall project maintainability.

This commit performs a **code style maintenance** operation by **applying consistent formatting** to handwritten Python files across several client libraries. Specifically, it **reorders import statements** within the **`google-cloud-automl` test suite** and the **`google-cloud-policytroubleshooter-iam`** and **`google-cloud-speech`** client packages. This ensures adherence to project-wide style guidelines for code not automatically formatted by `legacylibrarian`, improving overall code readability and consistency without introducing any functional changes.

This commit performs a **chore** to **fix inconsistencies and malformed URLs** within the `.repo-metadata.json` files for the **`google-analytics-data`** and **`google-cloud-memcache`** client libraries. Specifically, it corrects a malformed `issue_tracker` URL for Analytics Data and adds the `https://` scheme to the `product_documentation` URL for Memcache. These **metadata corrections** are applied to both the primary `packages/` directories and their corresponding `.librarian/generator-input/` locations. This ensures **data quality** and prevents future extraneous diffs when these APIs are next generated, maintaining consistency across the repository's metadata.

This commit introduces a new `tag_format` configuration option to the **Librarian state file** (`.librarian/state.yaml`), specifically for the **datastore library**. This **configuration update** is a **chore** that enables specifying how tags are formatted or managed within the datastore. By adding this setting, the commit lays the groundwork for enhanced control over tag representation and processing within the datastore's operations. This change primarily affects the **Librarian state management system** and the **datastore library's** tagging capabilities.

This commit performs a **chore** by cleaning up the `.librarian/state.yaml` configuration. It **removes non-existent sample and system test file patterns** from the `preserve_regex` lists across multiple libraries, which were previously used by `legacy-librarian`. This **maintenance** task simplifies the migration process from `legacy-librarian` to `librarian` by ensuring that `librarian`'s "keep" list only references actual, existing files, thereby preventing potential issues during the transition.

This commit performs a **maintenance chore and refactoring** within the **`internal/librariangen`** module by **removing all support for the legacy `protoc`/gRPC plugins**. Specifically, the `bazel/parser.go` now **explicitly errors** when detecting the deprecated gRPC plugin in Bazel build files, preventing silent omissions of gRPC output. All related logic has been stripped from the `protoc/protoc.go` build functions and `ConfigProvider` interface, along with corresponding test cases. This change simplifies the codebase and ensures a **hard failure** for outdated configurations, without affecting currently generated code.

This commit is a **maintenance chore** that **restores the CloudBuild configuration** for the **`librariangen`** project. It re-introduces the `cloudbuild-exitgate.yaml` file, which defines the necessary steps for the automated **building and pushing of a Docker image**. This ensures the continuous integration and deployment pipeline for `librariangen` is correctly configured, facilitating its automated release process.

This commit performs **maintenance** by **removing** the **legacy OwlBot postprocessor** from the `internal/postprocessor` module. This component has become obsolete as the project has fully transitioned to using **Librarian** for postprocessing tasks. The change **cleans up internal tooling** by eliminating unused code and infrastructure, as the associated Google Cloud Build trigger has already been deleted. This streamlines the codebase and ensures that only active and relevant postprocessing mechanisms are maintained.

This commit performs a **maintenance chore** by updating the Docker image reference for the **Librarian service's** `librarian-go` component. It specifically modifies the `.librarian/state.yaml` configuration file to point to a new `sha256` hash for the `librarian-go` image. This ensures that the **Librarian service** will deploy and run using the latest specified version of its core Go-based component, incorporating any recent changes or improvements from that image.

fix(librariangen): don't run tests from librariangen (#13336)

This commit performs a **maintenance update** by bumping the `librarian-go` image SHA in the `.librarian/state.yaml` configuration file. This ensures the **Librarian system** operates with the latest version of its core component, potentially incorporating new features or fixes. Additionally, it **onboards new client libraries** by adding repository metadata for the **Capacity Planner API v1beta**, **GKE Recommender API v1**, and **SaaS Service Management API v1beta1** APIs. This integration expands the scope of client libraries managed or tracked by the Librarian system.

This commit **updates the Cloud Client Libraries for the Storage API**, incorporating a **feature enhancement** and **documentation improvements** through an automated generation process. Specifically, it **makes the `return_partial_success` and `unreachable` fields public** for the `ListBucket` operation, providing users with more detailed information from these calls. Concurrently, the commit includes general **documentation updates and formatting** across the `storage` library to improve clarity. This **maintenance** update ensures the client library reflects the latest API definitions and offers enhanced data visibility for bucket listing.

This commit **refactors** the **`internal/librariangen`** tool to align with recent upstream changes in the `librarian` project. It **renames the `release-init` command to `release-stage`**, updating all corresponding Go code, command handlers like `releaseStageFunc`, documentation in `README.md`, and test scripts. This **maintenance** effort ensures the Go container's release process remains compatible with the updated `librarian` API, specifically impacting the **release staging functionality** and its associated tooling and configuration. The change propagates across `.gitignore` entries, `main.go` command definitions, `release/release.go` function names like `Stage`, and various `run-*.sh` test scripts.

This **maintenance chore** updates the **client library version metadata** within generated snippet configuration files across multiple Google Cloud services. It regenerates `snippet_metadata.json` files for **BigQuery**, **Logging**, and **Storage** client libraries, ensuring they reflect their most recently released versions (e.g., BigQuery from 1.71.0 to 1.72.0). This update guarantees that code snippets accurately reference the current client library versions. Crucially, this commit also signifies a **process change**, integrating this metadata regeneration directly into the Librarian release PR workflow, replacing previous OwlBot updates.

This commit primarily **updates the `librarian-go` image** to a new version (`sha256:ec5a10e927e3b3cdc457b23974879644572ab204864f353b19bf35d0af227678`), ensuring the project leverages the latest build environment. As part of this **maintenance** effort, the `.librarian/state.yaml` configuration file is reformatted and its entries are adjusted for the **`bigtable`**, **`gkerecommender`**, and **`pubsub/v2`** libraries. Furthermore, a **bug fix** is applied to correct file permissions by removing the executable bit from generated Go files within the `pubsub/v2/apiv1` directory. These changes collectively streamline the build process and maintain configuration integrity across several core components.

This commit introduces a **bug fix** within the **`librariangen` internal tool's postprocessor**, specifically addressing how Go modules are initialized. It modifies the `goModInit` function in `internal/librariangen/postprocessor/postprocessor.go` to now accept and correctly utilize the module path when executing the `go mod init` command. The `PostProcess` function has been updated to supply this critical path, ensuring that generated Go modules are properly named and configured. This change prevents potential issues with module resolution and dependency management for projects processed by `librariangen`, with corresponding test updates in `TestPostProcess` to verify the correct behavior.

This commit performs a **maintenance chore** by **removing legacy configuration files** that are no longer needed. Specifically, these configurations became obsolete after the **Librarian migration**, streamlining the project's overall setup. This cleanup effort ensures that the codebase maintains only current and relevant settings, improving clarity and reducing potential for misconfiguration across the project.