Stripe: tax_type can now return "digital_excise_tax", "utility_users_tax"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects tax_type on tax_rate reachable from 543 operations.

New values: digital_excise_tax, utility_users_tax.

can now return "digital_excise_tax", "utility_users_tax"

Who is affected

Code that reads Stripe's tax_rate objects, used by 543 Stripe operations.

Before and after

Where	Before	After
tax_rate.tax_type	"amusement_tax", "communications_tax", "gst", "hst", "igst", "jct", "lease_tax", "mass_transit_parking_tax", "parking_tax", "pst", "qst", "retail_delivery_fee", "rst", "sales_tax", "service_tax", "vat"	"amusement_tax", "communications_tax", "digital_excise_tax", "gst", "hst", "igst", "jct", "lease_tax", "mass_transit_parking_tax", "parking_tax", "pst", "qst", "retail_delivery_fee", "rst", "sales_tax", "service_tax", "utility_users_tax", "vat"

Code that breaks

switch (response.tax_type) {
  // existing branches …
  // no branch for "digital_excise_tax"
  // no branch for "utility_users_tax"
  default:
    throw new Error("unexpected tax_type");
}

Based on Stripe’s published API specification. How severity is decided.