$ the-wire · showcase
python-genai 3.0.0 defaults to Gemini API v1
By RepoJournal · Filed · About Google · Composed from the cited sources · methodology
python-genai's 3.0.0 release moves the Gemini Developer API default from v1beta to v1, with retry, sampling-precision, and storage telemetry work filling in behind it.
v3.0.0 googleapis/python-genai
by release-please[bot]
Clients targeting the Gemini Developer API now default to API version v1 instead of v1beta, and the release notes state there is no effect on Gemini Enterprise (Vertex AI) defaults for clients with vertexai=True or enterprise=. Anything pinned to v1beta-only behavior, including unreleased surface, needs an explicit version before upgrading.
fix(interactions): retries = attempts - 1 googleapis/python-genai
HttpRetryOptions.attempts counts the original request, but _translate_retry_config was passing it straight through as RetryConfig.max_retries, so attempts=0 and attempts=1 each still retried once. The mapping is now max(attempts - 1, 0), and an unset attempts falls back to the SDK-wide default.
Add `low`, `high`, and `highest` sampling precision modes to `jax.random.normal` google/jax
jax.random.normal gains an optional mode parameter of "low", "high", or "highest", defaulting to "low" and controlled by the jax_random_normal_mode config option. mode="low" preserves the current erf_inv path, which cuts off around +/-5.3 standard deviations for float32; the new modes draw on a full word of random bits to reach further into the tails.
Gate HIGHEST-accuracy tanh and logistic numerics on config flags. google/jax
Two temporary flags, jax_tanh_sech_jvp and jax_accurate_logistic, both defaulting to False, gate the closed (tanh, sech^2) JVP rules and the exp(-|x|) logistic lowering for HIGHEST-accuracy lax.tanh and lax.logistic. The stated purpose is to let callers migrate before either change is enabled by default.
fix(auth): prevent race conditions during mTLS cert rotation on 401 responses googleapis/google-cloud-python
The auth change adds thread safety around client certificate rotation triggered by 401 responses, addressing a race condition in the transports. Separately, gapic-generator 1.44.2 defaults client_options.api_endpoint to the transport host so OpenTelemetry spans carry the right endpoint, storage work landed an 11-instrument OpenTelemetry metrics recorder, and shard_map rules now cover lax.slice_...
Action items
- → Upgrade python-genai to 3.0.0 and pin api_version explicitly if you depend on v1beta behavior googleapis/python-genai [plan]