mirror of
https://github.com/google/adk-docs.git
synced 2026-09-14 16:16:59 +08:00
Shahin Saadati
e040a94029
* Bump adk-docs to adk-kotlin 1.0.0
KT-23. adk-docs compiles its Kotlin snippets against the pinned SDK, so no 1.0
feature can be documented until this pin moves. Prerequisite only - no snippets,
no prose about 1.0 features.
Moves the examples pin (core, webserver, processor, a2a) and the install
instructions readers copy from, which track the pin for the same reason they did
at 0.8.0: leaving them behind hands newcomers an SDK older than the snippets on
the same page.
THIS DOES NOT BUILD YET, and cannot until the artifacts are published:
> Could not find com.google.adk:google-adk-kotlin-core:1.0.0.
> Could not find com.google.adk:google-adk-kotlin-webserver:1.0.0.
> Could not find com.google.adk:google-adk-kotlin-a2a:1.0.0.
Maven Central carries 0.8.0 as the newest release for every artifact today, and
google/adk-kotlin has no v1.0.0 tag. The PR is a draft until the release lands.
Two comments that pinned third-party versions against adk-kotlin 0.8.0's
catalog - Ktor 2.3.13 and a2a-java-sdk-client 1.0.0.Final - now say the match
was made against 0.8.0 and needs re-checking, rather than restating it as though
it still held. A major release is exactly where a transitive version moves.
Also note the version string is assumed to be `1.0.0`. If the release is cut as
`1.0.0-rc.1` or similar, these five coordinates need to match it.
* Bump the A2A quickstart's dependency to 1.0.0 as well
Missed on the first pass, and the reason is worth recording: the sweep used
`google-adk-kotlin[a-z-]*:0\.8\.0`, whose character class has no digits, so it
silently skipped `google-adk-kotlin-a2a` - the one artifact with a digit in its
name. Every other coordinate matched, so the search looked exhaustive and was
not.
The corrected pattern is `google-adk-kotlin[a-z0-9-]*:[0-9]+\.[0-9]+\.[0-9]+`.
Run repo-wide it now finds five live coordinates in the examples build file and
seventeen in the docs, all at 1.0.0, and nothing left below it.
* Bump every adk-kotlin coordinate to 1.0.0
main moved to 0.9.0 (#2191) after this branch was cut, so the merge above
took main wholesale and this re-applies the 1.0 pin on top. Two coordinates
are new since the branch was opened and were never in the original bump:
- `google-adk-kotlin-litertlm` in `docs/agents/models/litert-lm.md`
- `google-adk-kotlin-integrations` in
`docs/integrations/bigquery-agent-analytics.md` (arrived with #2147, the
reconciliation the original PR description flagged as owed)
Also bumps the two tag-pinned `adk-kotlin/blob/v0.8.0` source links in
`docs/agents/llm-agents.md`. Those point at `SchemaUtils` and `LlmAgent` to
back a claim about how Kotlin validates output schemas; pinned to a tag five
releases behind, they document what 0.8 did, not what a reader on 1.0 runs.
19 coordinates and 2 permalinks. No `com.google.adk:google-adk-kotlin-*`
coordinate below 1.0.0 remains anywhere in the repo.
Deliberately untouched, because they record history rather than a pin:
the ~42 `Kotlin vX.Y.Z` support badges (bumping them would assert that e.g.
artifacts first shipped in Kotlin 1.0), and the "added in adk-kotlin 0.8.0"
/ "Since adk-kotlin 0.7.0" comments in CapitalAgent.kt and
CountInvocationPlugin.kt.
Still unbuildable and still a draft: Maven Central's newest
google-adk-kotlin-core is 0.9.0 and google/adk-kotlin's newest tag is v0.9.0,
so there is no 1.0.0 to resolve. `verify_snippets.py --fast` passes L3, L5 and
L6 and refuses L0 for exactly that reason -- no grounding source exists at the
target version. The bundled Dokka API reference under docs/api-reference/kotlin
still renders 0.5.0 across 1,674 files and cannot be regenerated until the tag
exists; it remains on the pre-merge checklist.