Skip to content

Modules and versions

ModuleImport
Coregithub.com/go-steer/core-models (the root package coremodels, plus llm, usage, callctx, retry, auth, profile, toolwire, kvmetrics, pricing, dialect/openaichat, dialect/openairesp, dialect/anthropic, dialect/gemini and dialect/gemini/vertexcache)
ADK v2 adaptergithub.com/go-steer/core-models/adkv2

A consumer requires the core module and the adapter. The ADK v1 adapter, adkv1, was deprecated in v0.6.6 (its last release) once both products moved to ADK v2, and has since been deleted; its tags stay fetchable from the module proxy.

Each module is tagged separately, Go’s convention for nested modules:

  • v0.x.y for the core;
  • adkv2/v0.x.y for the adapter.

core-models is pre-1.0 and its API may change between minor versions.

llm mirrors ADK’s model types, so genai types are part of core-models’ public API. That is a settled decision (design D7, #69): a genai major, or a breaking change to one of these types or a type they are built from, is a core-models major, and before 1.0 a minor with an API Change entry. The dependency floors below bound the exposure: the core requires the lowest genai either product uses.

The types, by the package whose exported API carries them:

Packagegenai typesWhere
llmContent, GenerateContentConfigRequest
llmContent, CitationMetadata, FinishReason, GenerateContentResponseUsageMetadata, GroundingMetadata, LogprobsResult, TranscriptionResponse
toolwireFunctionDeclarationEntry, EntryFor
dialect/geminiBackendOptions
dialect/geminiCachesClient.Caches
dialect/geminiContent, ToolContextCacheInitFn
dialect/geminiGroundingMetadataGroundingEvidence
dialect/gemini/vertexcacheCachedContent, CreateCachedContentConfig, UpdateCachedContentConfig, DeleteCachedContentConfig, DeleteCachedContentResponseCachesClient
dialect/gemini/vertexcacheContent, ToolManager.Init

No other core package exposes a genai type. adkv2 exposes ADK v2 types, which is its purpose; the core module imports no ADK package.

A library’s requirements become the minimum versions its consumers get. The core module therefore requires the lowest genai version either product uses, so importing core-models never upgrades a product’s genai underneath its own tests.

The same rule sets github.com/anthropics/anthropic-sdk-go at v1.43.0, core-agent’s version; mast is on v1.78.0. The anthropic dialect uses nothing newer.

Google credentials come from cloud.google.com/go/auth, at the version genai already requires, so the core adds no module for them. Claude on Vertex AI uses those credentials too, rather than the SDK’s vertex package, which would bring in golang.org/x/oauth2 and google.golang.org/api.

For the same reason the oauth2_client_credentials auth kind does its token exchange itself (one form POST, cached on expires_in) rather than through golang.org/x/oauth2/clientcredentials, which would add a module, and so a floor, for both products.

Exceptions are made for security fixes:

FloorWhy
google.golang.org/grpc v1.83.1GO-2026-6348. Both products were already at or above it
golang.org/x/net v0.60.0GO-2026-6611, -6612 and -6617 (HTTP/2). This raises both products’ floor, to the fixed version

Each go.mod also carries toolchain go1.26.11 for the standard library’s fixes to the HTTP/2, crypto/x509 and net/http (GO-2026-6859) issues. A toolchain line governs only this repository’s own builds and CI; it is not imposed on consumers. They need Go 1.26.11 or later in their own builds to be clear of those issues.