ohmayr

This commit introduces a **new integration test presubmit job** within the **CI/CD pipeline** for the **`gapic-generator` package**. It modifies `.github/workflows/gapic-generator-tests.yml` to add an `integration` job that executes Bazel integration tests. This **maintenance** enhancement ensures that changes to the `gapic-generator` are thoroughly validated against integration scenarios before merging, thereby improving the overall stability and reliability of the generated code.

This commit implements a **CI/CD optimization** by introducing path filters to all **`django-spanner` presubmit workflows**. It updates numerous GitHub Actions workflow files, such as `django-spanner-django3.2_tests_against_emulator1.yml`, to leverage the `dorny/paths-filter` action. This **maintenance** change ensures that the extensive `django-spanner` test suites, covering various Django and Python versions against emulators and mockservers, are now **conditionally executed** only when relevant code changes are detected. The primary impact is a significant **reduction in CI/CD run times and resource consumption** for pull requests that do not modify the `django-spanner` module.

This commit introduces a **configuration change** to the `.librarian/config.yaml` file, specifically adding an entry to **block future releases** for the `google-django-spanner` library. This is a **maintenance chore** aimed at controlling the release pipeline and preventing new versions of this particular component from being published. The change directly impacts the **release management system**, ensuring no new deployments for `google-django-spanner` will occur.

This commit introduces a **new capability** to the **Google Shopping Merchant Accounts** client library by adding the `CreateTestAccount` RPC to the `AccountsService`. This allows users to programmatically create test-only Merchant Center accounts, significantly enhancing testing workflows. Concurrently, this update includes several **documentation improvements** across various services and types, such as clarifying `Account.account_name` restrictions, `CheckoutSettings.eligible_destinations` usage, and updating `Program` and `Region` definitions. These changes provide developers with a new testing utility and clearer guidance for interacting with the **Merchant Accounts API**.

This commit **re-onboards** the `google-cloud-network-connectivity` library by **reverting its previous removal** from the `.librarian/state.yaml` configuration file. This **maintenance** change re-enables the library for management by the **`librarian` system**, following the successful deployment of a namespace fix. Consequently, the `google-cloud-network-connectivity` library is now properly tracked and integrated within the project's dependency management.

This commit **temporarily removes** the `google-cloud-documentai-toolbox` dependency from the **Librarian automation** workflows. This **maintenance chore** addresses critical failures occurring during the `generate` and `release` steps of the automation process, which were being caused by the problematic dependency. By removing `google-cloud-documentai-toolbox`, the commit ensures that the **Librarian automation** can successfully complete its tasks, preventing further disruptions to the build and release processes. The dependency will be re-introduced once the root cause of the failures is investigated and resolved, as tracked in issue #4705.

This commit performs a **maintenance chore** by updating the **`librarian` configuration system** to manage the build process for the **`google-cloud-documentai-toolbox`** library. It specifically sets the `generate_blocked` flag to `true` within the `.librarian/config.yaml` file for this particular library. This configuration change is essential to **unblock the automatic generation process** for `google-cloud-documentai-toolbox`, allowing its necessary build artifacts to be created.

This commit performs **maintenance** by updating the project's release configuration. Specifically, it adds the `google-cloud-documentai-toolbox` library to the `.librarian/config.yaml` file, marking it as release blocked. This crucial change **unblocks automated releases** for the `documentai-toolbox` module, allowing it to be properly managed within the project's continuous integration and deployment pipeline. The update ensures that the release process can proceed smoothly for this specific library.

This commit performs a **maintenance chore** by **removing** the `google-cloud-network-connectivity` entry from the `state.yaml` configuration file. This action **prevents the librarian automation** from prematurely regenerating and releasing the `google-cloud-network-connectivity` package. The package is currently not ready for public release, and this change ensures its release is deferred until necessary prerequisites are met, specifically awaiting a related internal change. This temporary hold on the **release process** for the `google-cloud-network-connectivity` module ensures stability and proper readiness before deployment.

This commit introduces a **configuration update** by modifying the `.gitignore` file. It specifically adds `.ruff_cache` to the ignore list, preventing Ruff's generated cache directory from being tracked by Git. This **maintenance chore** ensures that temporary build artifacts from the **Python linting tool Ruff** are not committed to the repository. The change improves repository hygiene and avoids unnecessary file churn in version control, streamlining the development workflow.

This commit is a **maintenance chore** focused on **improving code style and formatting** within the **GKE Hub client library**. It applies consistent formatting across several files, including `configmanagement.py`, `rbacrolebindingactuation_v1/__init__.py`, and `feature.py` within the `google-cloud-gke-hub` package. Changes involve reordering and combining import statements, adding blank lines after definitions, and reformatting function calls to align with established style guidelines. This work enhances code readability and maintainability without introducing any functional changes or affecting the library's behavior.

This commit performs a **maintenance chore** by **updating code formatting** within the **Google Cloud Translate V2 client library**. Specifically, it reformats a string literal in the `detect_language` method of `client.py` and removes an unnecessary blank line. This change ensures the handwritten code adheres to `ruff check` compatibility, improving code readability and consistency. The work is purely stylistic, with no functional impact on the `google-cloud-translate` package's behavior.

This commit performs a **maintenance chore** by **updating the development tooling** for several packages. Specifically, it **migrates the linting and code formatting sessions in `noxfile.py` from `black` and `isort` to `ruff`** for the **`google-cloud-access-context-manager`**, **`google-cloud-audit-log`**, **`googleapis-common-protos`**, and **`grpc-google-iam-v1`** modules. This change standardizes the code style enforcement and results in **minor stylistic adjustments** across numerous `*.pyi` type stub files within these packages, ensuring consistent formatting and potentially faster linting.

This **chore** commit **updates the `synthtool` dependency** used within the project's **`.generator` Docker environment**. It achieves this by pinning the `synthtool` repository to a newer Git commit hash in the `.generator/Dockerfile`. This update ensures the code generation process leverages an improved version of `synthtool`, specifically supporting a "no-install nox format" for enhanced efficiency and consistency in development and CI/CD workflows.

This commit **updates the librarian container CLI tool** to leverage **`ruff` for code formatting and import sorting**, effectively replacing the previously used `black` and `isort` tools. This **maintenance chore** modifies the `_run_post_processor` function within `.generator/cli.py` to integrate `ruff` into the post-processing workflow. The change also updates the `.generator/requirements.in` and `.generator/requirements-test.in` files, ensuring the development and testing environments correctly reflect this **tooling migration** and streamline code quality checks.

This commit performs **maintenance** on the **Grafeas client post-processing script** to enhance its robustness. Specifically, it updates the **regex patterns** within `unique-grafeas-client.yaml` to more effectively handle diverse whitespace and multi-line scenarios. This improvement ensures the post-processing for the **Grafeas client** is more reliable and resilient to variations in input, preventing potential parsing issues.

This commit performs a **maintenance update** by bumping the `synthtool` dependency's git checkout hash within the **`.generator/Dockerfile`**. The primary purpose of this update is to enable `synthtool` to **skip virtual environment creation** when executing `nox format` commands. This change streamlines the **development workflow** by improving the efficiency of code formatting operations within the project's code generation environment.

This commit performs a **dependency update**, incrementing the `gapic-generator` tool from version 1.30.7 to 1.30.8 within the project's `.generator/requirements.in` file. This **maintenance chore** ensures that the **code generation process** for **Google Cloud client libraries** utilizes the latest version of the generator. By updating this core dependency, the project benefits from any new features, bug fixes, or performance improvements introduced in the `gapic-generator` tool, potentially leading to more robust and efficient generated client code.

This commit performs a **maintenance chore** by updating the **`gapic-generator`** library version within the project's dependency management. Specifically, it bumps the version from `1.30.7` to `1.30.8` as recorded in the `packages/gapic-generator/.librarian/state.yaml` configuration file. This **internal dependency update** ensures the project utilizes the latest stable release of the `gapic-generator`, incorporating any upstream improvements or fixes. The change is confined to the `librarian` state configuration for the `gapic-generator` package, with no direct code changes to the generator itself.

This commit addresses a **`mypy` type checking issue** within the **`gapic-generator`** by reformatting `__func__` attribute assignments in the `async_client.py.j2` template. It also **enhances the `mypy` configuration** for generated code by updating `mypy.ini.j2` to include explicit package bases and incremental checking. This **maintenance and bug fix** ensures that generated Python clients will pass `mypy` checks more reliably and benefit from improved type safety. Furthermore, the **CI workflow** is updated to run `mypy` and formatting checks on the generated output, enforcing these quality standards across all generated GAPIC libraries.