Lingqing Gan

This commit introduces a **new `Literals` pipeline stage** within the **`google-cloud-firestore` library**, allowing users to initiate a data pipeline directly from a fixed set of in-memory document objects. A new `literals` method on `PipelineSource` facilitates the creation of pipelines utilizing this stage. This **new capability** significantly enhances the flexibility of **Firestore data pipelines**, enabling direct injection of predefined data for testing, mock scenarios, or specific processing workflows. Comprehensive unit and system-level end-to-end tests have been added to validate the correct functionality of this new stage.

This commit introduces **new object functions** to the **Google Cloud Firestore client library**, specifically enhancing its **pipeline expression capabilities**. It adds `map_set()`, `map_keys()`, `map_values()`, and `map_entries()` methods to the `Expression` class in `google.cloud.firestore_v1.pipeline_expressions.py`. This **new capability** allows users to perform advanced manipulation of map-like data structures directly within Firestore operations, such as setting new key-value pairs or extracting map components. Comprehensive unit and system tests have been added to validate the correctness and reliability of these new map functions, providing developers with more powerful tools for data processing.

This commit **introduces a new capability** to the **`google-cloud-firestore` client library** by adding support for various array manipulation functions. It enhances the `Expression` class in `pipeline_expressions.py` with methods like `array_first`, `array_last`, `array_slice`, `array_maximum`, and `array_index_of_all`. This allows users to perform complex array operations directly within Firestore queries, providing more powerful data processing capabilities. Comprehensive unit tests in `test_pipeline_expressions.py` and system tests in `array.yaml` have been added to ensure the correctness of these new array expression methods.

This commit introduces **new string expression capabilities** to the `google-cloud-firestore` library, significantly enhancing its data manipulation features. It adds a comprehensive set of methods to the `Expression` class within the **pipeline expressions** module, enabling advanced string operations like regular expression matching (`regex_find`, `regex_find_all`), splitting (`split`), repeating (`string_repeat`), replacing (`string_replace_all`, `string_replace_one`), indexing (`string_index_of`), and trimming (`ltrim`, `rtrim`). This **new capability** empowers users to perform complex string transformations directly within Firestore operations, reducing the need for external processing. The functionality is thoroughly validated through new unit and system-level end-to-end tests.

This commit introduces **new mathematical expressions** to the **`google-cloud-firestore` client library**, specifically adding `Rand` and `Trunc` capabilities. It provides a new `trunc` method to the `Expression` class for performing **truncation** and a `Rand` expression for **random number generation** within pipeline operations. This **new feature** enhances the library's expression language, allowing users to perform these operations directly in their queries. Comprehensive **unit and system-level tests** have been added to validate the functionality of these new expressions.

This commit introduces **new aggregation functions** to the **Google Cloud Firestore client library**, enhancing its query capabilities. It adds `array_agg()`, `array_agg_distinct()`, `first()`, and `last()` methods to the `Expression` class within `google.cloud.firestore_v1/pipeline_expressions.py`. This **new capability** allows users to perform advanced array and element selection aggregations directly in Firestore queries. The feature is thoroughly validated with new unit tests for the `Expression` class methods and comprehensive system-level end-to-end tests to ensure correct functionality and integration.

This commit performs a **maintenance chore** by updating the repository metadata for the **`google-cloud-hypercomputecluster`** client library. Specifically, it changes the default API version from `v1beta` to **`v1`**, signifying the API's graduation to a stable release. The API description within the `.repo-metadata.json` files has also been updated to reflect these changes. This ensures that client library generation and default configurations will now target the stable **`v1` API** for Hypercompute Cluster, providing a more robust and officially supported interface.

This commit **adds a new `.repo-metadata.json` configuration file** for the **`google-cloud-vectorsearch`** client library. This is a **maintenance chore** specifically addressing an issue where the `librarian` code generation tool failed due to the absence of this required metadata file. By providing this configuration, the commit **enables the successful generation** of the `google-cloud-vectorsearch` client library, ensuring its proper integration and future updates within the project.

This commit performs **test maintenance** for the **`google-cloud-bigquery-storage`** library by adding `cryptography` and `cachetools` to its test dependencies. Specifically, `cryptography` is now included in the system test extras and `cachetools` in the unit test dependencies within `noxfile.py`. This change **resolves `ModuleNotFoundError` test failures** that arose due to recent updates in the `google-auth-library-python` package, ensuring the **`bigquery-storage`** test suite can execute successfully and reliably.

This commit prepares for the **release of version 3.40.0** of the **`google-cloud-bigquery`** library, updating its internal version string and the Librarian state configuration. This **maintenance** release introduces **new features** for timestamp handling, specifically adding support for picosecond timestamps in `load_table` and `list_rows` operations, and enabling the specification of timestamp precision within table schemas. Merging this pull request will automatically trigger the official release process, making these enhanced capabilities available to users of the `google-cloud-bigquery` client library.

This commit introduces **support for picosecond timestamp precision** across key BigQuery client library operations. It enables users to **load data with picosecond timestamps** by adding `timestamp_target_precision` to `LoadJobConfig`, and to **query and list rows** while preserving this precision using new `timestamp_precision` parameters in `client.query` and `client.list_rows`. Internal helpers like `_helpers.timestamp_to_py` and `_job_helpers._to_query_request` were updated to correctly handle and format the new precision. This **new capability** significantly enhances the `google-cloud-bigquery` library's ability to work with high-resolution time series data, ensuring data fidelity during both ingestion and retrieval.

This commit introduces a **new feature** to the **`google-cloud-bigquery` client library**, enabling users to specify `timestamp_precision` for `TIMESTAMP` type fields within **BigQuery table schemas**. It adds a new `TimestampPrecision` enum in `enums.py` and extends the `SchemaField` class in `schema.py` to properly handle this attribute during initialization, API representation, and deserialization. This **enhancement** provides more granular control over timestamp data storage, allowing for definitions like picosecond precision. Comprehensive unit and system tests were added to validate the correct functioning of this new capability.

This commit **introduces support for Python 3.14** within the `bigquery-magics` package, primarily by **extending its continuous integration and testing infrastructure**. It updates the GitHub Actions unit test workflow and `noxfile.py` to include Python 3.14 in the test matrix, alongside adding new Kokoro presubmit configurations for both prerelease dependencies and system tests specific to this Python version. This **feature enhancement** ensures that the `bigquery-magics` package is thoroughly tested and compatible with the latest Python release, providing stability and future-proofing for users.

This commit **adds support for Python 3.14** for the **`google-auth` library**. It introduces new **Kokoro CI configurations** and updates **Nox test configurations** to include Python 3.14 in the continuous integration and testing matrix. A new `constraints-3.14.txt` file is added to manage dependencies specific to this Python version, and existing **asynchronous tests** in `test_aiohttp_requests.py` are updated to use `pytest.mark.asyncio` for proper execution. This **new capability** ensures the `google-auth` library and its samples are thoroughly tested and compatible with the latest Python release, improving its long-term maintainability and developer experience.

This commit introduces **test infrastructure improvements** within the **`google-auth` package** by managing temporary directories used for secrets. The `decrypt-secrets.sh` script now **creates the `system_tests/data` directory** if it doesn't exist, ensuring a reliable location for decrypted secrets during testing. Conversely, the `encrypt-secrets.sh` script has been updated to **clean up this temporary directory** after encryption, maintaining a pristine state. This **chore** enhances the robustness and reliability of the **system test environment** by preventing issues related to missing or leftover temporary data.

This commit performs a **maintenance chore** to address a **testing framework compatibility issue** within the `google-auth` package. It updates **asynchronous pytest fixtures** in `packages/google-auth/tests/transport/aio/test_sessions.py` by wrapping them in synchronous functions. This change is specifically implemented to suppress the `PytestRemovedIn9Warning`. The primary impact is ensuring the **asynchronous transport test suite** remains functional and warning-free with newer Pytest versions, preventing potential disruptions to continuous integration.

This commit performs **maintenance** on the **test suite** for the `google-cloud-logging` package to address deprecation warnings and update Python version support. It modifies `pytest.ini` to ignore various `DeprecationWarning` and `FutureWarning` messages, specifically those related to the `credentials_file` argument and Python version compatibility, preventing test failures due to expected deprecations. Concurrently, `noxfile.py` is updated to set the `DEFAULT_PYTHON_VERSION` for Nox sessions to 3.10 and remove Python 3.7 and 3.8 from the unit test matrix. This ensures the testing environment is aligned with current Python support and tests run cleanly without irrelevant warnings.

This commit performs a **dependency update** for the `google-auth` library, advancing its version to `2.43.0` as part of a Librarian release. This **maintenance** update incorporates new **mTLS features** into the authentication library, enabling mTLS automatically when specific certificate sources are detected. This enhancement improves secure communication with Google APIs by leveraging client certificates. The update primarily affects the `google-auth` module's internal version string in `version.py` and its configuration in `.librarian/state.yaml`.

This commit performs a **testing configuration update** for the `google-cloud-dns` package, **removing Python 3.7 and 3.8** from the unit test execution matrix. The `noxfile.py` in `packages/google-cloud-dns` is modified to explicitly define unit test sessions for Python versions 3.9 through 3.14. This **maintenance change** streamlines the **testing infrastructure** by focusing automated tests on currently supported Python environments. Additionally, an `owlbot.py` rule was introduced to ensure this `noxfile.py` update persists through future post-processing.

This commit **updates the test configuration** for the `google-cloud-dns` package to suppress specific Python warnings. It **modifies `pytest.ini`** to add `filterwarnings` directives, ignoring both `DeprecationWarning` and `FutureWarning` during test runs. This **maintenance improvement** ensures that the **testing suite** executes cleanly across Python versions **3.8, 3.9, and 3.10**, preventing unnecessary test failures or noisy output caused by these expected warnings.