mirror of
https://github.com/googleapis/genai-toolbox.git
synced 2026-01-09 07:28:05 -05:00
5156db26213db09ab89ec99958790de7c72126d0
1179 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
release-please[bot]
|
5156db2621 |
chore(main): release 0.20.0 (#1921)
🤖 I have created a release *beep* *boop* --- ## [0.20.0](https://github.com/googleapis/genai-toolbox/compare/v0.19.1...v0.20.0) (2025-11-14) ### Features * Added prompt support for toolbox ([#1798](https://github.com/googleapis/genai-toolbox/issues/1798)) ([v0.20.0 |
||
|
Yuan Teoh
|
7c67bcc810 |
chore: update hugo version (#1950)
update hugo version |
||
|
Yuan Teoh
|
f6804420b9 |
chore: embed ToolsetConfig into Toolset (#1885)
To keep a persistent backend storage for configuration, we will have to keep a single source of truth. This involves supporting bi-directional conversion between ToolsetConfig and Toolset. This PR make the following changes: * Embed ToolsetConfig in Toolset * Add `ToConfig()` to extract ToolsetConfig from Toolset. |
||
|
Yuan Teoh
|
927881ffb9 |
chore: embed Config into Auth (#1865)
To keep a persistent backend storage for configuration, we will have to keep a single source of truth. This involves supporting bi-directional conversion between Config and AuthService. This PR make the following changes: * Embed Config in AuthService * Add `ToConfig()` to extract Config from AuthService. |
||
|
google-labs-jules[bot]
|
42c8dd7ddd |
chore: embed Config into Tool (#1875)
To keep a persistent backend storage for configuration, we will have to keep a single source of truth. This involves supporting bi-directional conversion between Config and Tool. This PR make the following changes: * Embed Config in Tool * Add `ToConfig()` to extract Config from Tool. Jules PR --- *PR created automatically by Jules for task [11947649751737965380](https://jules.google.com/task/11947649751737965380)* --------- Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com> Co-authored-by: Yuan Teoh <yuanteoh@google.com> |
||
|
Yuan Teoh
|
ae0c29254a |
chore: embed Config into Source (#1864)
To keep a persistent backend storage for configuration, we will have to keep a single source of truth. This involves supporting bi-directional conversion between Config and Source. This PR make the following changes: * Embed Config in Source * Add `ToConfig()` to extract Config from Source. |
||
|
Ajaykumar Yadav
|
46b072c3f4 |
docs(alloydb): fix redirection link of the cgc doc for alloydb (#1936)
## Description In the docs `Connect from you IDE > AlloyDB Admin API with MCP` The previous link was `pointing to wrong documentation`, corrected the link now it will be pointing to the correct documentation for the `how to connect you ide with alloydb-pg-admin` - [x] removed the wrong link: https://cloud.google.com/alloydb/docs/quickstart/create-and-connect - [x] added the correct link: https://cloud.google.com/alloydb/docs/connect-ide-using-mcp-toolbox ## PR Checklist - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involves a breaking change |
||
|
Yuan Teoh
|
4aabb4aaca |
chore: move parameters to internal/util (#1907)
To facilitate the transition of moving invocation implementation to Source, we will have to move parameter to `internal/util`. This approach is crucial because certain parameters may not be fully resolvable pre-implementation. Since both `internal/sources` and `internal/tools` will need access to `parameters`, it will be more relevant to move parameters implementation to utils. |
||
|
Srividya Reddy
|
897c63dcea |
feat(tools): add list_indexes, list_sequences tools for postgres (#1765)
## Description Adds the following tools for Postgres: (1) list_indexes: Lists available user indexes in a given database. (2) list_sequences: Lists all the sequences in the database ordered by sequence name. list_indexes: <img width="1708" height="816" alt="Screenshot 2025-10-21 at 10 24 30 PM" src="https://github.com/user-attachments/assets/d1888f53-6013-4beb-b0dc-b94f3d66135e" /> <img width="1914" height="1017" alt="Screenshot 2025-10-22 at 8 23 16 AM" src="https://github.com/user-attachments/assets/7c185ef4-4550-4bb2-8051-0eca8f40dc7b" /> list_sequences: <img width="2539" height="902" alt="Screenshot 2025-10-22 at 8 04 25 AM" src="https://github.com/user-attachments/assets/f22cfaad-412b-4df2-99f3-ee813f538ff7" /> <img width="1082" height="610" alt="Screenshot 2025-10-22 at 8 06 07 AM" src="https://github.com/user-attachments/assets/102ed3ca-33f6-409f-9ba1-363c9e15d5d3" /> > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #1738 |
||
|
Averi Kitsch
|
22b5aca395 |
ci: add product specific automation (#1906)
## Description Set up product specific automation ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [ ] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here> |
||
|
Mend Renovate
|
57f6220b9e |
chore(deps): update module google.golang.org/genai to v1.35.0 (#1941)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [google.golang.org/genai](https://redirect.github.com/googleapis/go-genai) | `v1.34.0` -> `v1.35.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>googleapis/go-genai (google.golang.org/genai)</summary> ### [`v1.35.0`](https://redirect.github.com/googleapis/go-genai/releases/tag/v1.35.0) [Compare Source](https://redirect.github.com/googleapis/go-genai/compare/v1.34.0...v1.35.0) ##### Features - Add `ToGenerationConfig` method to `GenerateContentConfig`. fixes [#​506](https://redirect.github.com/googleapis/go-genai/issues/506) ([bd53df4]( |
||
|
Mend Renovate
|
c451015509 |
chore(deps): update module github.com/trinodb/trino-go-client to v0.330.0 (#1940)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/trinodb/trino-go-client](https://redirect.github.com/trinodb/trino-go-client) | `v0.329.0` -> `v0.330.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>trinodb/trino-go-client (github.com/trinodb/trino-go-client)</summary> ### [`v0.330.0`](https://redirect.github.com/trinodb/trino-go-client/releases/tag/v0.330.0) [Compare Source](https://redirect.github.com/trinodb/trino-go-client/compare/v0.329.0...v0.330.0) <!-- Release notes generated using configuration in .github/release.yml at v0.330.0 --> #### What's Changed ##### Other changes - Fix tests for Trino>=477 by [@​nineinchnick](https://redirect.github.com/nineinchnick) in [#​161](https://redirect.github.com/trinodb/trino-go-client/pull/161) - Add support to disable explicitPrepare by using Config.FormatDSN by [@​Flgado](https://redirect.github.com/Flgado) in [#​160](https://redirect.github.com/trinodb/trino-go-client/pull/160) - Add Client Tags Support by [@​Flgado](https://redirect.github.com/Flgado) in [#​155](https://redirect.github.com/trinodb/trino-go-client/pull/155) **Full Changelog**: <https://github.com/trinodb/trino-go-client/compare/v0.329.0...v0.330.0> </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> |
||
|
Luka Fontanilla
|
ef63860559 |
feat: adding generate embed url functionality (#1877)
## Description > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution This PR adds a new tool to the Looker MCP Toolbox, that enables the user authenticated to the Looker Source to generate authenticated embed urls for dashboards, looks and queries. When combined with other tools that already exist in the Looker toolbox, this enables searching existing content and providing authenticated urls to them OR creating authenticated urls from queries generated via Natural Language. The embed urls will create an embed session for the user and can be opened directly or added to an iframe `src` attribute to provide a smooth Embedded Analytics setup. Additionally this PR adds a new optional parameter to the Looker source called `SessionLength` which an admin setting up the Looker source can set to determine how long the Embed sessions last for. ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [ X] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ X] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ X] Code coverage does not decrease (if any source code was changed) - [X ] Appropriate docs were updated (if necessary) - [ X] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #1876 https://github.com/googleapis/genai-toolbox/issues/1876 --------- Co-authored-by: Luka Fontanilla <maluka@google.com> Co-authored-by: Dr. Strangelove <drstrangelove@google.com> |
||
|
Dr. Strangelove
|
a89191d8bb |
ci: increase time for lint to run (#1947)
## Description As the codebase gets bigger, the linter takes longer to run. Currently it is running in an average of 3 minutes and 30 seconds or so, but occasionally goes to 4 minutes, which causes a failure since it hits the timeout. The unit tests all take 10 to 15 minutes to run, so setting the timeout to 10m will give plenty of time for the linter to run. |
||
|
Yuan Teoh
|
13a682f407 |
ci(mcp-registry): fix path to retrieve version string (#1946)
## Description Fix path to retrieve Version string from server.json |
||
|
Twisha Bansal
|
dc7c62c951 |
test: improve root test coverage (#1929)
## Description > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here> |
||
|
Yuan Teoh
|
aec8897805 |
feat(mcp-registry): publish custom tools server to mcp-registry (#1834)
## Description This PR adds a new [github action](https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/github-actions.md) workflow to publish Toolbox to mcp-registry. This only publishes the custom tools server, prebuilt-tools will be added in a different PR once this is successful. The workflow will be triggered on (1) any new release tag (v*) or (2) manually via GHA workflow dispatch. It will grab the version number from the `server.json` file. The server.json file will be updated by release please during every release. Note: server that are published in the mcp-registry is immutable. In cases where we successfully published a server and would like to make an update, we will have to update the `version` field in `.registry/server.json` and manually publish another server with a new version. ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #1659 Issue at mcp-registry to support GAR ([#427](https://github.com/modelcontextprotocol/registry/issues/427)) |
||
|
Srividya Reddy
|
a4c9287aec |
feat(tools/postgres): add list_triggers, database_overview tools for postgres (#1912)
## Description Adds the following tools for Postgres: (1) list_triggers: Lists triggers in the database. . (2) database_overview: Fetches the current state of the PostgreSQL server. list_triggers: <img width="1712" height="703" alt="Screenshot 2025-11-09 at 8 16 53 PM" src="https://github.com/user-attachments/assets/1974e303-b559-4efc-b129-444ba97c7715" /> <img width="874" height="513" alt="Screenshot 2025-11-09 at 8 19 43 PM" src="https://github.com/user-attachments/assets/59ddcd15-224b-4e9a-906d-ec2645835873" /> database_overview: <img width="1521" height="683" alt="Screenshot 2025-11-09 at 8 53 03 PM" src="https://github.com/user-attachments/assets/4ae86e74-aa78-410c-a9cc-f33ae3268fb6" /> <img width="850" height="241" alt="Screenshot 2025-11-09 at 8 49 53 PM" src="https://github.com/user-attachments/assets/abae2c7a-5f3e-4433-86de-3606e3298ec5" /> > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #1738 |
||
|
Niraj Nandre
|
2c228ef4f2 |
feat(tool/mysql): Set default host and port for MySQL source (#1922)
## Description This pull request addresses issue [#29](https://github.com/gemini-cli-extensions/mysql/issues/29) by implementing default connection values for the MySQL data source. When a user does not specify a host or port, the connection will now automatically default to localhost:3306. ### Detailed Changes 1. **internal/prebuiltconfigs/tools/mysql.yaml** - Added the default values to host and port.Specifically, they are now host: ${MYSQL_HOST:localhost} and port: ${MYSQL_PORT:3306}.This allows the configuration loader to directly use "localhost" or "3306" as a fallback if the MYSQL_HOST or MYSQL_PORT environment variables are not set. **Testing and Validation** To ensure the changes work correctly and are compatible with MySQL-like databases, the feature was manually tested against a MariaDB instance running in a Docker container. The testing process involved the following steps: 1. A local testdb database with a products table was created in the MariaDB container. 2. For Gemini CLI integration, the ~/.gemini/settings.json file was configured to point to a local build of the toolbox executable. 3. The toolbox was launched in UI mode using the **_./toolbox --prebuilt=mysql --ui_** command. 4. Two connection scenarios were tested to validate the new logic. **Test 1: Default Connection (Host/Port Unset)** The MYSQL_HOST and MYSQL_PORT environment variables were unset. The application correctly defaulted to localhost:3306 and successfully connected to the testdb database. <img width="2087" height="1102" alt="Screenshot 2025-11-11 11 31 45 PM" src="https://github.com/user-attachments/assets/a8ef5f92-eaca-472f-a0df-e2b3c0c027da" /> **Test 2: Explicit Connection (Host/Port Set)** The MYSQL_HOST and MYSQL_PORT environment variables were explicitly set. The application correctly used these values, overriding the defaults and establishing a successful connection. <img width="2073" height="958" alt="Screenshot 2025-11-11 6 12 44 PM" src="https://github.com/user-attachments/assets/4b9b8838-091f-4c78-9e3b-97768323693c" /> **Result:** In both scenarios, the list_tables prebuilt tool was executed via the Toolbox UI, which successfully returned the products table from the testdb database, confirming the changes work as expected. Screenshot of list_tables execution from the Toolbox UI: <img width="2251" height="1240" alt="result" src="https://github.com/user-attachments/assets/f1c5372d-acc0-4551-af2d-fa1ee4b228d7" /> ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involve a breaking change 🛠️ Fixes [#29](https://github.com/gemini-cli-extensions/mysql/issues/29) --------- Co-authored-by: prernakakkar-google <158031829+prernakakkar-google@users.noreply.github.com> |
||
|
Mend Renovate
|
1e9c4762a5 |
chore(deps): update module github.com/valkey-io/valkey-go to v1.0.68 (#1920)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [github.com/valkey-io/valkey-go](https://redirect.github.com/valkey-io/valkey-go) | `v1.0.67` -> `v1.0.68` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>valkey-io/valkey-go (github.com/valkey-io/valkey-go)</summary> ### [`v1.0.68`](https://redirect.github.com/valkey-io/valkey-go/releases/tag/v1.0.68): 1.0.68 [Compare Source](https://redirect.github.com/valkey-io/valkey-go/compare/v1.0.67...v1.0.68) ### Changes - feat: add new DELEX, DIGEST, MSETEX commands; extend SET and XREADGROUP - feat: FIPS-compliant SHA-1 loading option for Lua scripts without performance penalty - feat: add EPSILON option to VSIM #### Contributors We'd like to thank all the contributors who worked on this release! [@​FZambia](https://redirect.github.com/FZambia) and [@​rueian](https://redirect.github.com/rueian) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> |
||
|
Valipishetty Sathwik
|
7e6e88a21f |
feat(tool/Postgresql): Set default host and port for Postgresql source (#1927)
### Description This pull request addresses issue #41 by implementing default connection values for the Postgresql data source. When a user does not specify a host or port, the connection will now automatically default to `localhost:5432`. --- ### Detailed Changes - **docs/en/reference/prebuilt-tools.md** -updated the env variables host and port to optional in the doc - **internal/prebuiltconfigs/tools/postgres.yaml** - Added the default values to host and port. Specifically, they are now `host: ${POSTGRES_HOST:localhost}` and `port: ${POSTGRES_PORT:5432}`. This allows the configuration loader to directly use `"localhost"` or `"5432"` as a fallback if the `POSTGRES_HOST` or `POSTGRES_PORT` environment variables are not set. --- ### PR Checklist Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly: - [ ] Make sure you reviewed CONTRIBUTING.md - [ ] Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add ! if this involve a breaking change 🛠️ **Fixes** #41 --------- Co-authored-by: Averi Kitsch <akitsch@google.com> |
||
|
Mend Renovate
|
b2ea4b7b8f |
chore(deps): update dependency pytest to v9.0.1 (#1938)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `==9.0.0` -> `==9.0.1` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.0.1`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.1) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/9.0.0...9.0.1) ### pytest 9.0.1 (2025-11-12) #### Bug fixes - [#​13895](https://redirect.github.com/pytest-dev/pytest/issues/13895): Restore support for skipping tests via `raise unittest.SkipTest`. - [#​13896](https://redirect.github.com/pytest-dev/pytest/issues/13896): The terminal progress plugin added in pytest 9.0 is now automatically disabled when iTerm2 is detected, it generated desktop notifications instead of the desired functionality. - [#​13904](https://redirect.github.com/pytest-dev/pytest/issues/13904): Fixed the TOML type of the verbosity settings in the API reference from number to string. - [#​13910](https://redirect.github.com/pytest-dev/pytest/issues/13910): Fixed <span class="title-ref">UserWarning: Do not expect file\_or\_dir</span> on some earlier Python 3.12 and 3.13 point versions. #### Packaging updates and notes for downstreams - [#​13933](https://redirect.github.com/pytest-dev/pytest/issues/13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. #### Contributor-facing changes - [#​13891](https://redirect.github.com/pytest-dev/pytest/issues/13891), [#​13942](https://redirect.github.com/pytest-dev/pytest/issues/13942): The CI/CD part of the release automation is now capable of creating GitHub Releases without having a Git checkout on disk -- by `bluetech` and `webknjaz`. - [#​13933](https://redirect.github.com/pytest-dev/pytest/issues/13933): The tox configuration has been adjusted to make sure the desired version string can be passed into its `package_env` through the `SETUPTOOLS_SCM_PRETEND_VERSION_FOR_PYTEST` environment variable as a part of the release process -- by `webknjaz`. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNzMuMSIsInVwZGF0ZWRJblZlciI6IjQxLjE3My4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> |
||
|
Twisha Bansal
|
cfd4b18dee |
docs: fix prompt message (#1930)
## Description > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here> |
||
|
Twisha Bansal
|
d2576cbc38 |
docs: add links (#1931)
## Description > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here> |
||
|
Twisha Bansal
|
cd56ea44fb |
feat: Added prompt support for toolbox (#1798)
## Description Added MCP prompt support in the toolbox server. - No updates needed corresponding to https://github.com/googleapis/genai-toolbox/pull/1828/files. ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes https://github.com/googleapis/genai-toolbox/issues/1040 --------- Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> Co-authored-by: dishaprakash <57954147+dishaprakash@users.noreply.github.com> Co-authored-by: Mend Renovate <bot@renovateapp.com> Co-authored-by: Averi Kitsch <akitsch@google.com> Co-authored-by: Anmol Shukla <shuklaanmol@google.com> Co-authored-by: Harsh Jha <83023263+rapid-killer-9@users.noreply.github.com> Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> Co-authored-by: Kurtis Van Gent <31518063+kurtisvg@users.noreply.github.com> Co-authored-by: Dr. Strangelove <drstrangelove@google.com> Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com> Co-authored-by: Dave Borowitz <dborowitz@google.com> |
||
|
Sri Varshitha
|
12bdd95459 |
feat(source/alloydb, source/cloud-sql-postgres,source/cloud-sql-mysql,source/cloud-sql-mssql): Use project from env for alloydb and cloud sql control plane tools (#1588)
## Description --- This change introduces the `DefaultProject` field for the `alloydb-admin` and `cloud-sql-admin` sources. This field allows the alloydb and cloud sql control plane tools to use the project value from the environment variables (Ex: `ALLOYDB_POSTGRES_PROJECT`) if it is already set instead of asking the user. ## PR Checklist --- > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes: https://github.com/gemini-cli-extensions/alloydb/issues/47 --------- Co-authored-by: Averi Kitsch <akitsch@google.com> |
||
|
Mend Renovate
|
61739300be |
chore(deps): update dependency llama-index-llms-google-genai to v0.7.3 (#1886)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | llama-index-llms-google-genai | `==0.7.1` -> `==0.7.3` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> |
||
|
Mend Renovate
|
3b140f5006 |
chore(deps): update module google.golang.org/adk to v0.1.0 (#1887)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [google.golang.org/adk](https://redirect.github.com/google/adk-go) | `v0.0.0-20251105212711-ccd61aa4a1b6` -> `v0.1.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> |
||
|
Mend Renovate
|
84e826a93e |
chore(deps): update module golang.org/x/oauth2 to v0.33.0 (#1909)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | golang.org/x/oauth2 | `v0.32.0` -> `v0.33.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> Co-authored-by: Averi Kitsch <akitsch@google.com> |
||
|
Mend Renovate
|
edd739c490 |
chore(deps): update dependency pytest to v9 (#1911)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [pytest](https://redirect.github.com/pytest-dev/pytest) ([changelog](https://docs.pytest.org/en/stable/changelog.html)) | `==8.4.2` -> `==9.0.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>pytest-dev/pytest (pytest)</summary> ### [`v9.0.0`](https://redirect.github.com/pytest-dev/pytest/releases/tag/9.0.0) [Compare Source](https://redirect.github.com/pytest-dev/pytest/compare/8.4.2...9.0.0) ### pytest 9.0.0 (2025-11-05) #### New features - [#​1367](https://redirect.github.com/pytest-dev/pytest/issues/1367): **Support for subtests** has been added. `subtests <subtests>` are an alternative to parametrization, useful in situations where the parametrization values are not all known at collection time. Example: ```python def contains_docstring(p: Path) -> bool: """Return True if the given Python file contains a top-level docstring.""" ... def test_py_files_contain_docstring(subtests: pytest.Subtests) -> None: for path in Path.cwd().glob("*.py"): with subtests.test(path=str(path)): assert contains_docstring(path) ``` Each assert failure or error is caught by the context manager and reported individually, giving a clear picture of all files that are missing a docstring. In addition, `unittest.TestCase.subTest` is now also supported. This feature was originally implemented as a separate plugin in [pytest-subtests](https://redirect.github.com/pytest-dev/pytest-subtests), but since then has been merged into the core. > \[!NOTE] > This feature is experimental and will likely evolve in future releases. By that we mean that we might change how subtests are reported on failure, but the functionality and how to use it are stable. - [#​13743](https://redirect.github.com/pytest-dev/pytest/issues/13743): Added support for **native TOML configuration files**. While pytest, since version 6, supports configuration in `pyproject.toml` files under `[tool.pytest.ini_options]`, it does so in an "INI compatibility mode", where all configuration values are treated as strings or list of strings. Now, pytest supports the native TOML data model. In `pyproject.toml`, the native TOML configuration is under the `[tool.pytest]` table. ```toml # pyproject.toml [tool.pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The `[tool.pytest.ini_options]` table remains supported, but both tables cannot be used at the same time. If you prefer to use a separate configuration file, or don't use `pyproject.toml`, you can use `pytest.toml` or `.pytest.toml`: ```toml # pytest.toml or .pytest.toml [pytest] minversion = "9.0" addopts = ["-ra", "-q"] testpaths = [ "tests", "integration", ] ``` The documentation now (sometimes) shows configuration snippets in both TOML and INI formats, in a tabbed interface. See `config file formats` for full details. - [#​13823](https://redirect.github.com/pytest-dev/pytest/issues/13823): Added a **"strict mode"** enabled by the `strict` configuration option. When set to `true`, the `strict` option currently enables - `strict_config` - `strict_markers` - `strict_parametrization_ids` - `strict_xfail` The individual strictness options can be explicitly set to override the global `strict` setting. The previously-deprecated `--strict` command-line flag now enables strict mode. If pytest adds new strictness options in the future, they will also be enabled in strict mode. Therefore, you should only enable strict mode if you use a pinned/locked version of pytest, or if you want to proactively adopt new strictness options as they are added. See `strict mode` for more details. - [#​13737](https://redirect.github.com/pytest-dev/pytest/issues/13737): Added the `strict_parametrization_ids` configuration option. When set, pytest emits an error if it detects non-unique parameter set IDs, rather than automatically making the IDs unique by adding <span class="title-ref">0</span>, <span class="title-ref">1</span>, ... to them. This can be particularly useful for catching unintended duplicates. - [#​13072](https://redirect.github.com/pytest-dev/pytest/issues/13072): Added support for displaying test session **progress in the terminal tab** using the [OSC 9;4;](https://conemu.github.io/en/AnsiEscapeCodes.html#ConEmu_specific_OSC) ANSI sequence. When pytest runs in a supported terminal emulator like ConEmu, Gnome Terminal, Ptyxis, Windows Terminal, Kitty or Ghostty, you'll see the progress in the terminal tab or window, allowing you to monitor pytest's progress at a glance. This feature is automatically enabled when running in a TTY. It is implemented as an internal plugin. If needed, it can be disabled as follows: - On a user level, using `-p no:terminalprogress` on the command line or via an environment variable `PYTEST_ADDOPTS='-p no:terminalprogress'`. - On a project configuration level, using `addopts = "-p no:terminalprogress"`. - [#​478](https://redirect.github.com/pytest-dev/pytest/issues/478): Support PEP420 (implicit namespace packages) as <span class="title-ref">--pyargs</span> target when `consider_namespace_packages` is <span class="title-ref">true</span> in the config. Previously, this option only impacted package imports, now it also impacts tests discovery. - [#​13678](https://redirect.github.com/pytest-dev/pytest/issues/13678): Added a new `faulthandler_exit_on_timeout` configuration option set to "false" by default to let <span class="title-ref">faulthandler</span> interrupt the <span class="title-ref">pytest</span> process after a timeout in case of deadlock. Previously, a <span class="title-ref">faulthandler</span> timeout would only dump the traceback of all threads to stderr, but would not interrupt the <span class="title-ref">pytest</span> process. \-- by `ogrisel`. - [#​13829](https://redirect.github.com/pytest-dev/pytest/issues/13829): Added support for configuration option aliases via the `aliases` parameter in `Parser.addini() <pytest.Parser.addini>`. Plugins can now register alternative names for configuration options, allowing for more flexibility in configuration naming and supporting backward compatibility when renaming options. The canonical name always takes precedence if both the canonical name and an alias are specified in the configuration file. #### Improvements in existing functionality - [#​13330](https://redirect.github.com/pytest-dev/pytest/issues/13330): Having pytest configuration spread over more than one file (for example having both a `pytest.ini` file and `pyproject.toml` with a `[tool.pytest.ini_options]` table) will now print a warning to make it clearer to the user that only one of them is actually used. \-- by `sgaist` - [#​13574](https://redirect.github.com/pytest-dev/pytest/issues/13574): The single argument `--version` no longer loads the entire plugin infrastructure, making it faster and more reliable when displaying only the pytest version. Passing `--version` twice (e.g., `pytest --version --version`) retains the original behavior, showing both the pytest version and plugin information. > \[!NOTE] > Since `--version` is now processed early, it only takes effect when passed directly via the command line. It will not work if set through other mechanisms, such as `PYTEST_ADDOPTS` or `addopts`. - [#​13823](https://redirect.github.com/pytest-dev/pytest/issues/13823): Added `strict_xfail` as an alias to the `xfail_strict` option, `strict_config` as an alias to the `--strict-config` flag, and `strict_markers` as an alias to the `--strict-markers` flag. This makes all strictness options consistently have configuration options with the prefix `strict_`. - [#​13700](https://redirect.github.com/pytest-dev/pytest/issues/13700): <span class="title-ref">--junitxml</span> no longer prints the <span class="title-ref">generated xml file</span> summary at the end of the pytest session when <span class="title-ref">--quiet</span> is given. - [#​13732](https://redirect.github.com/pytest-dev/pytest/issues/13732): Previously, when filtering warnings, pytest would fail if the filter referenced a class that could not be imported. Now, this only outputs a message indicating the problem. - [#​13859](https://redirect.github.com/pytest-dev/pytest/issues/13859): Clarify the error message for <span class="title-ref">pytest.raises()</span> when a regex <span class="title-ref">match</span> fails. - [#​13861](https://redirect.github.com/pytest-dev/pytest/issues/13861): Better sentence structure in a test's expected error message. Previously, the error message would be "expected exception must be \<expected>, but got \<actual>". Now, it is "Expected \<expected>, but got \<actual>". #### Removals and backward incompatible breaking changes - [#​12083](https://redirect.github.com/pytest-dev/pytest/issues/12083): Fixed a bug where an invocation such as <span class="title-ref">pytest a/ a/b</span> would cause only tests from <span class="title-ref">a/b</span> to run, and not other tests under <span class="title-ref">a/</span>. The fix entails a few breaking changes to how such overlapping arguments and duplicates are handled: 1. <span class="title-ref">pytest a/b a/</span> or <span class="title-ref">pytest a/ a/b</span> are equivalent to <span class="title-ref">pytest a</span>; if an argument overlaps another arguments, only the prefix remains. 2. <span class="title-ref">pytest x.py x.py</span> is equivalent to <span class="title-ref">pytest x.py</span>; previously such an invocation was taken as an explicit request to run the tests from the file twice. If you rely on these behaviors, consider using `--keep-duplicates <duplicate-paths>`, which retains its existing behavior (including the bug). - [#​13719](https://redirect.github.com/pytest-dev/pytest/issues/13719): Support for Python 3.9 is dropped following its end of life. - [#​13766](https://redirect.github.com/pytest-dev/pytest/issues/13766): Previously, pytest would assume it was running in a CI/CD environment if either of the environment variables <span class="title-ref">$CI</span> or <span class="title-ref">$BUILD\_NUMBER</span> was defined; now, CI mode is only activated if at least one of those variables is defined and set to a *non-empty* value. - [#​13779](https://redirect.github.com/pytest-dev/pytest/issues/13779): **PytestRemovedIn9Warning deprecation warnings are now errors by default.** Following our plan to remove deprecated features with as little disruption as possible, all warnings of type `PytestRemovedIn9Warning` now generate errors instead of warning messages by default. **The affected features will be effectively removed in pytest 9.1**, so please consult the `deprecations` section in the docs for directions on how to update existing code. In the pytest `9.0.X` series, it is possible to change the errors back into warnings as a stopgap measure by adding this to your `pytest.ini` file: ```ini [pytest] filterwarnings = ignore::pytest.PytestRemovedIn9Warning ``` But this will stop working when pytest `9.1` is released. **If you have concerns** about the removal of a specific feature, please add a comment to `13779`. #### Deprecations (removal in next major release) - [#​13807](https://redirect.github.com/pytest-dev/pytest/issues/13807): `monkeypatch.syspath_prepend() <pytest.MonkeyPatch.syspath_prepend>` now issues a deprecation warning when the prepended path contains legacy namespace packages (those using `pkg_resources.declare_namespace()`). Users should migrate to native namespace packages (`420`). See `monkeypatch-fixup-namespace-packages` for details. #### Bug fixes - [#​13445](https://redirect.github.com/pytest-dev/pytest/issues/13445): Made the type annotations of `pytest.skip` and friends more spec-complaint to have them work across more type checkers. - [#​13537](https://redirect.github.com/pytest-dev/pytest/issues/13537): Fixed a bug in which `ExceptionGroup` with only `Skipped` exceptions in teardown was not handled correctly and showed as error. - [#​13598](https://redirect.github.com/pytest-dev/pytest/issues/13598): Fixed possible collection confusion on Windows when short paths and symlinks are involved. - [#​13716](https://redirect.github.com/pytest-dev/pytest/issues/13716): Fixed a bug where a nonsensical invocation like `pytest x.py[a]` (a file cannot be parametrized) was silently treated as `pytest x.py`. This is now a usage error. - [#​13722](https://redirect.github.com/pytest-dev/pytest/issues/13722): Fixed a misleading assertion failure message when using `pytest.approx` on mappings with differing lengths. - [#​13773](https://redirect.github.com/pytest-dev/pytest/issues/13773): Fixed the static fixture closure calculation to properly consider transitive dependencies requested by overridden fixtures. - [#​13816](https://redirect.github.com/pytest-dev/pytest/issues/13816): Fixed `pytest.approx` which now returns a clearer error message when comparing mappings with different keys. - [#​13849](https://redirect.github.com/pytest-dev/pytest/issues/13849): Hidden `.pytest.ini` files are now picked up as the config file even if empty. This was an inconsistency with non-hidden `pytest.ini`. - [#​13865](https://redirect.github.com/pytest-dev/pytest/issues/13865): Fixed <span class="title-ref">--show-capture</span> with <span class="title-ref">--tb=line</span>. - [#​13522](https://redirect.github.com/pytest-dev/pytest/issues/13522): Fixed `pytester` in subprocess mode ignored all :attr\`pytester.plugins \<pytest.Pytester.plugins>\` except the first. Fixed `pytester` in subprocess mode silently ignored non-str `pytester.plugins <pytest.Pytester.plugins>`. Now it errors instead. If you are affected by this, specify the plugin by name, or switch the affected tests to use `pytester.runpytest_inprocess <pytest.Pytester.runpytest_inprocess>` explicitly instead. #### Packaging updates and notes for downstreams - [#​13791](https://redirect.github.com/pytest-dev/pytest/issues/13791): Minimum requirements on `iniconfig` and `packaging` were bumped to `1.0.1` and `22.0.0`, respectively. #### Contributor-facing changes - [#​12244](https://redirect.github.com/pytest-dev/pytest/issues/12244): Fixed self-test failures when <span class="title-ref">TERM=dumb</span>. - [#​12474](https://redirect.github.com/pytest-dev/pytest/issues/12474): Added scheduled GitHub Action Workflow to run Sphinx linkchecks in repo documentation. - [#​13621](https://redirect.github.com/pytest-dev/pytest/issues/13621): pytest's own testsuite now handles the `lsof` command hanging (e.g. due to unreachable network filesystems), with the affected selftests being skipped after 10 seconds. - [#​13638](https://redirect.github.com/pytest-dev/pytest/issues/13638): Fixed deprecated `gh pr new` command in `scripts/prepare-release-pr.py`. The script now uses `gh pr create` which is compatible with GitHub CLI v2.0+. - [#​13695](https://redirect.github.com/pytest-dev/pytest/issues/13695): Flush <span class="title-ref">stdout</span> and <span class="title-ref">stderr</span> in <span class="title-ref">Pytester.run</span> to avoid truncated outputs in <span class="title-ref">test\_faulthandler.py::test\_timeout</span> on CI -- by `ogrisel`. - [#​13771](https://redirect.github.com/pytest-dev/pytest/issues/13771): Skip <span class="title-ref">test\_do\_not\_collect\_symlink\_siblings</span> on Windows environments without symlink support to avoid false negatives. - [#​13841](https://redirect.github.com/pytest-dev/pytest/issues/13841): `tox>=4` is now required when contributing to pytest. - [#​13625](https://redirect.github.com/pytest-dev/pytest/issues/13625): Added missing docstrings to `pytest_addoption()`, `pytest_configure()`, and `cacheshow()` functions in `cacheprovider.py`. #### Miscellaneous internal changes - [#​13830](https://redirect.github.com/pytest-dev/pytest/issues/13830): Configuration overrides (`-o`/`--override-ini`) are now processed during startup rather than during `config.getini() <pytest.Config.getini>`. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR was generated by [Mend Renovate](https://mend.io/renovate/). View the [repository job log](https://developer.mend.io/github/googleapis/genai-toolbox). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0MS4xNTkuNCIsInVwZGF0ZWRJblZlciI6IjQxLjE1OS40IiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119--> |
||
|
release-please[bot]
|
cd8d68d464 |
chore(main): release 0.19.1 (#1901)
🤖 I have created a release *beep* *boop* --- ## [0.19.1](https://github.com/googleapis/genai-toolbox/compare/v0.19.0...v0.19.1) (2025-11-07) ### ⚠ BREAKING CHANGES * **tools/alloydbainl:** update AlloyDB AI NL statement order ([#1753](https://github.com/googleapis/genai-toolbox/issues/1753)) * **tools/bigquery-analyze-contribution:** Add allowed dataset support ([#1675](https://github.com/googleapis/genai-toolbox/issues/1675)) ([v0.19.1 |
||
|
Yuan Teoh
|
e3672a8b5e |
chore: release 0.19.1 (#1902)
Release-As: 0.19.1 |
||
|
Yuan Teoh
|
b85596d307 |
ci: add worker pool to release (#1900)
Added a new worker pool in release cloud build that uses `n2d-standard-64` machine, with disk size 100GB. removed the `machineType` since it's indicated in the worker pool. Release-As: 0.20.0 |
||
|
Yuan Teoh
|
207e7861d0 |
ci: add geminicli build step to continuous release (#1899)
Add an additional binary build step for gemini cli. The purpose of this is to mimic the build steps of versioned.release. However, we will not be storing that additional build. |
||
|
Yuan Teoh
|
6e297ee9e9 |
Revert release 0.19.0 docs version update (#1898)
Reverts googleapis/genai-toolbox#1781 docs version update |
||
|
release-please[bot]
|
78c4a8537e |
chore(main): release 0.19.0 (#1781)
🤖 I have created a release *beep* *boop* --- ## [0.19.0](https://github.com/googleapis/genai-toolbox/compare/v0.18.0...v0.19.0) (2025-11-07) ### ⚠ BREAKING CHANGES * **tools/alloydbainl:** update AlloyDB AI NL statement order ([#1753](https://github.com/googleapis/genai-toolbox/issues/1753)) * **tools/bigquery-get-dataset-info:** add allowed dataset support ([#1654](https://github.com/googleapis/genai-toolbox/issues/1654)) ### Features * Support `excludeValues` for parameters ([#1818](https://github.com/googleapis/genai-toolbox/issues/1818)) ([ |
||
|
dishaprakash
|
39957b93b8 |
chore: Update blunderbuss for OOO (#1895)
## Description Update blunderbuss for OOO ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here> |
||
|
Yuan Teoh
|
3c9efde848 |
chore: release 0.19.0 (#1892)
Release-As: 0.19.0 |
||
|
Yuan Teoh
|
1f833fb1a1 |
feat(healthcare): add support for healthcare source, tool and prebuilt config (#1853)
## Description Add support for healthcare source, tool and prebuilt config. This branch consist of all previously approved PRs. 🛠️ Fixes #1648 --------- Co-authored-by: Marwan Tammam <15021613+Quarz0@users.noreply.github.com> |
||
|
Yuan Teoh
|
22c0b4609d |
ci: update alloydb ai nl int test database (#1872)
Update AlloyDB AI NL integration test's database back to `test_database`. Previously a new database was created with new NL configuration in order to not break existing integration tests before merging PR #1753. `test_database` is updated with v1.0.4 AlloyDB AI NL extension. |
||
|
Yuan Teoh
|
1af43db6f2 |
test: add prebuilt tools test to all postgres source (#1874)
Move postgres prebuilt integration tests to `common.go` and `tool.go`. Run those tests from alloydbpg and cloudsqlpg as well. alloydbpg and cloudsqlpg integration test coverage calculate against the whole `internal/tools/postgres/` folder. If not added, the coverage will eventually drop below minimum requirement. |
||
|
Yuan Teoh
|
47bbbd8c7f |
ci: add commit sha and latest tag to continuous release image (#1869)
Add commit sha tag to continuous release image. Currently, we only include the ref_name tag (which will always show as `main` since we run the continuous release from the main branch), however, this will be replaced during every PR merge and it will be tough to find image of previous versions. With the commit sha tag, this will help user find the exact image that they are looking for. |
||
|
Yuan Teoh
|
559e2a22e0 |
fix: bigquery result column order (#1884)
Assigning job iterator value to an array instead of map to preserve
column order.
When assigning incoming values to map, sometimes the result is not in
order of statement. E.g. `SELECT id, name from ...` might turn into
`{"name": "name_value", "id":1}` rather than `{"id":1, "name":
"name_value"}`. Previously, during json marshaling, it will ALWAYS order
the map in alphabetical order. so that wasn't an issue.
With the implementation of `orderedmap` (#1852), the bigquery execute
sql tool will now preserves the column order during the marshaling
process. Due to this, bigquery's integration test is flaky and failed
when the map is reordered. This update assign incoming value as array
instead, preserving the actual order.
|
||
|
Dr. Strangelove
|
30857c2294 |
feat(tools/looker-run-dashboard): new run_dashboard tool (#1858)
## Description The run_dashboard tool will run the query associated with each tile of the dashboard and return the full set of query results. It enables the agent to answer questions like "Summarize this dashboard for me". --------- Co-authored-by: Yuan Teoh <45984206+Yuan325@users.noreply.github.com> |
||
|
Averi Kitsch
|
7e7b572bd2 |
docs: update architecture diagram (#1888)
## Description > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [ ] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [ ] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [ ] Ensure the tests and linter pass - [ ] Code coverage does not decrease (if any source code was changed) - [ ] Appropriate docs were updated (if necessary) - [ ] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here> |
||
|
Dr. Strangelove
|
937eff192e |
chore: fix linter action to error on lint issue (#1891)
lint action used to fix the issue rather than error |
||
|
Dr. Strangelove
|
27663f0a12 | chore(singlestore): fix lint issues (#1890) | ||
|
Dr. Strangelove
|
991e539f9c |
feat(tools/looker-run-look): modify run_look to show query origin (#1860)
… as coming from MCP Toolbox |
||
|
Mend Renovate
|
cd4ae81501 |
chore(deps): update dependency google-adk to v1.18.0 (#1850)
This PR contains the following updates: | Package | Change | Age | Confidence | |---|---|---|---| | [google-adk](https://redirect.github.com/google/adk-python) ([changelog](https://redirect.github.com/google/adk-python/blob/main/CHANGELOG.md)) | `==1.15.1` -> `==1.18.0` | [](https://docs.renovatebot.com/merge-confidence/) | [](https://docs.renovatebot.com/merge-confidence/) | --- ### Release Notes <details> <summary>google/adk-python (google-adk)</summary> ### [`v1.18.0`](https://redirect.github.com/google/adk-python/blob/HEAD/CHANGELOG.md#1180-2025-11-05) [Compare Source](https://redirect.github.com/google/adk-python/compare/v1.17.0...v1.18.0) ##### Features - **\[ADK Visual Agent Builder]** - Core Features - Visual workflow designer for agent creation - Support for multiple agent types (LLM, Sequential, Parallel, Loop, Workflow) - Agent tool support with nested agent tools - Built-in and custom tool integration - Callback management for all ADK callback types (before/after agent, model, tool) - Assistant to help you build your agents with natural language - Assistant proposes and writes agent configuration yaml files for you - Save to test with chat interfaces as normal - Build and debug at the same time in adk web! - **\[Core]** - Add support for extracting cache-related token counts from LiteLLM usage ([4f85e86]( |
||
|
Pavlo Mishchenko
|
40b9dbab08 |
feat(singlestore): Add SingleStore Source and Tools (#1333)
## Description --- - This PR adds SingleStore database source and tools. The code is mostly based on MySQL source and tools, and it uses the same go-mysql driver. - https://github.com/singlestore-labs/singlestoredb-dev-image can be used to deploy a test SingleStore instance. In this PR the default port is set to 3308 so the command would be ```docker run \ -d --name singlestoredb-dev \ -e ROOT_PASSWORD="YOUR SINGLESTORE ROOT PASSWORD" \ -p 3308:3306 ghcr.io/singlestore-labs/singlestoredb-dev:latest ``` ## PR Checklist --- > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/langchain-google-alloydb-pg-python/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes https://github.com/googleapis/genai-toolbox/issues/1348 --------- Co-authored-by: Wenxin Du <117315983+duwenxin99@users.noreply.github.com> |