What shipped in Google on August 27, 2026?

JAX just removed a deprecated API, and Google Cloud is wiring up OpenTelemetry. In total, 25 commits and 21 pull requests landed.

Who contributed to Google on August 27, 2026?

7 developers shipped this update, including jax authors, copybara-service, Amer Elsheikh, Mark Daoust, codyoss, quirogas, and chalmerlowe.

What were the notable Google updates?

Delete shard_alike from JAX. Use explicit mode as the replacement: https://docs.jax.dev/en/latest/201/sharding.html, Merge pull request #40215 from ROCm:users/gulsumgudukbay/deprecate-rocm-smi-cli-upstream, and feat(api-core): add tracer_provider to ClientOptions for OTel support.

Google

JAX, the GenAI SDK, and the Cloud libs - Google's open source layer

Pick a date

Topics: AI / ML Python Full archive →

The Wire · Showcase

JAX Deletes shard_alike

By RepoJournal · Filed 06:58 UTC on August 27, 2026 · About Google

7 people shipped this

chalmerlowe @chalmerlowe 2 cited

jax authors @Google-ML-Automation 1 cited

copybara-service @copybara-service 1 cited

codyoss @codyoss 1 cited

quirogas @quirogas 1 cited

Amer Elsheikh @QEDady

Mark Daoust @MarkDaoust

JAX just removed a deprecated API, and Google Cloud is wiring up OpenTelemetry.

The JAX team deleted shard_alike, pushing users to explicit mode [1], while ROCm deprecates its smi CLI upstream [2]. Google Cloud is adding tracer_provider to ClientOptions for OTel support [3], and the SQLAlchemy Spanner dialect gets robust session-isolated test databases to end race conditions [4]. python-genai adds Java API reference examples , and google-cloud-python regenerates with librarian v0.39.0 [6]. A new Map Management library lands for v2 [5]. The vendor says "the test runs shared a single hardcoded database using a static configuration file" [4].

Action items

→ Review JAX code for shard_alike usage and migrate to explicit mode before upgrading google/jax [immediate]
→ Adopt tracer_provider in ClientOptions for OTel tracing googleapis/google-cloud-python [plan]
→ Monitor ROCm smi CLI deprecation for JAX on AMD google/jax [monitor]

References

[1] Delete shard_alike from JAX. Use explicit mode as the replacement: https://docs.jax.dev/en/latest/201/sharding.html ↗ google/jax
[2] Merge pull request #40215 from ROCm:users/gulsumgudukbay/deprecate-rocm-smi-cli-upstream google/jax
[3] feat(api-core): add tracer_provider to ClientOptions for OTel support ↗ googleapis/google-cloud-python
[4] fix(sqlalchemy-spanner): robust session-isolated test databases and clean lifecycle management ↗ googleapis/google-cloud-python
[5] feat(google/maps/mapmanagement/v2): onboard a new library ↗ googleapis/google-cloud-python
[6] chore: update librarian to v0.39.0 ↗ googleapis/google-cloud-python

Quick answers

What shipped in Google on August 27, 2026?: JAX just removed a deprecated API, and Google Cloud is wiring up OpenTelemetry. In total, 25 commits and 21 pull requests landed.
Who contributed to Google on August 27, 2026?: 7 developers shipped this update, including jax authors, copybara-service, Amer Elsheikh, Mark Daoust, codyoss, quirogas, and chalmerlowe.
What were the notable Google updates?: Delete shard_alike from JAX. Use explicit mode as the replacement: https://docs.jax.dev/en/latest/201/sharding.html, Merge pull request #40215 from ROCm:users/gulsumgudukbay/deprecate-rocm-smi-cli-upstream, and feat(api-core): add tracer_provider to ClientOptions for OTel support.

GENAI SHIPS 2.20.0 WHILE API-CORE PATCHES A YANKED RELEASE

If you pulled the latest google-cloud-python, check your Firestore calls: the api-core path_template change broke gRPC requests, and the fix is landing now.