|
3 | 3 | All notable changes to this project will be documented in this file. |
4 | 4 |
|
5 | 5 |
|
| 6 | +## [1.9.0] - 2026-10-06 |
| 7 | + |
| 8 | +- **Usage telemetry is now on by default.** Each command writes one log entry to your own Google Cloud project with the command name, exit code, error class, duration, and CLI, Python and OS versions, never arguments or file contents. Its purpose is to provide users with analytics regarding their tool use, process efficiency, and help diagnose potential issues. The request also sends Google the CLI, Python and OS versions, CPU architecture and command name for usage analytics; no sensitive data is sent. Opt out with `AGENTS_CLI_TELEMETRY=0` or `DO_NOT_TRACK=1`. `agents-cli info` now always shows whether telemetry is on. |
| 9 | +- `agents-cli deploy --key` encrypts an Agent Runtime agent with a customer-managed Cloud KMS key (CMEK), so deploys work in projects that enforce `constraints/gcp.restrictNonCmekServices`. The key can only be set when the agent is created, and `deploy --list` shows it in a new Encryption column. |
| 10 | + - https://github.com/google/agents-cli/issues/83 |
| 11 | +- `agents-cli deploy --dry-run` checks an Agent Runtime deployment against Google Cloud: enabled APIs, the target engine, IAM permissions, `actAs` on the service account, and secrets. A definite problem exits with code 1, and a check that cannot run only warns. A dry run now makes read-only network calls. A real deploy is unchanged. |
| 12 | +- `agents-cli deploy` reports unsupported flags in one format, `<flag> is only supported for <targets> deployments (current target: <target>)`, and names only the flags you passed. An empty value for such a flag, such as `--key ""` on Cloud Run, is now rejected instead of ignored. Scripts that match the old error text may need updating. |
| 13 | +- New ADK Python projects set `GOOGLE_GENAI_USE_ENTERPRISE=true` instead of the deprecated `GOOGLE_GENAI_USE_VERTEXAI`. Existing projects keep working: `agents-cli deploy` to Agent Runtime respects whichever name your `.env` sets. Go projects keep the old name. |
| 14 | +- New ADK Go projects enable the `gofmt` and `goimports` formatters, so `agents-cli lint` reports formatting issues and `lint --fix` fixes them. |
| 15 | +- Re-applying the Terraform generated by this release, for example with `agents-cli infra single-project` or `infra cicd`, no longer replaces the BigQuery log sink tables once logs have arrived. The replacement deleted every exported log. `completions_view` also gains a `service_version` column with the deployment revision. Run `agents-cli scaffold upgrade` to get this in an existing project. |
| 16 | +- Scaffolded ADK projects no longer append a duplicate `JSONRPC 0.3` interface to the agent card on every request to `.well-known/agent-card.json`. |
| 17 | + - https://github.com/google/agents-cli/issues/84 |
| 18 | +- A tool that exists but cannot run, such as `uv.exe` blocked by AppLocker on Windows, now fails with a clear error naming the tool and the OS reason instead of a `PermissionError` traceback. |
| 19 | + - https://github.com/google/agents-cli/issues/61 |
| 20 | +- Installed extensions no longer print a warning on every command. A notice appears only when a command overridden by an extension runs. |
| 21 | + - https://github.com/google/agents-cli/issues/91 |
| 22 | + |
6 | 23 | ## [1.8.0] - 2026-09-30 |
7 | 24 |
|
8 | 25 | - New flag for`agents-cli scaffold upgrade`: `--force`. A fallback for when the 3-way merge cannot run or leaves too many conflicts, similar to the existing flag for `agents-cli scaffold enhance`. It generates only the new template and overwrites the scaffolding files: |
|
0 commit comments