google_gax (patched)

Patched fork of google_gax v0.4.1 for compatibility with Tesla >= 1.18.3.

Why this fork exists

Tesla 1.18.3 (June 2, 2026) introduced strict validation of multipart field names via assert_quoted_string_safe!/2 as part of security fixes for CVE-2026-48598. The upstream google_gax (last release: 2021, unmaintained) passes atoms (:metadata, :data) as multipart field names, which Tesla now rejects with a FunctionClauseError.

Changes from upstream

• connection.ex: Convert atom field names to strings (to_string/1) before passing to Tesla.Multipart.add_field/4 and Tesla.Multipart.add_file/3
• connection.ex: Use string tuples for headers ({"Content-Type", ...}) instead of atom tuples ({:"Content-Type", ...})
• mix.exs: Relaxed mime and poison version constraints

Usage

# mix.exs
{:google_gax, github: "workshops-de/google_gax", override: true}

Upstream

• Hex: https://hex.pm/packages/google_gax
• Source: https://github.com/googleapis/elixir-google-api/tree/master/clients/gax
• Open issue: https://github.com/googleapis/elixir-google-api/issues/12817