Andrew Minion

Makes sense. Updated results for 80fd004: ```php [ "0: Date" => ">=08/30/2024", "0: _kf_ContactIDWorker" => "31195", "1: _kf_ContactIDWorker" => "17159", "2: omit" => "true", "2: _kf_ContactIDWorker" => "10956", ] ```

Awesome; thanks!

> Why not supporting unit enums as well? Done

I’m seeing this too, when creating a payment intent with this data: ```php $stripe = new \Stripe\StripeClient('sk_test_Tm42SIKZinsVvyBCHb01UHcI'); $stripe->paymentIntents->create([ 'amount' => 2000, 'currency' => 'usd', 'automatic_payment_methods' => [ 'enabled' => true,...

Sounds like maybe it just needs to be rebuilt against a newer OpenAPI spec?

Some more information: - Using stripe-mock installed via homebrew on macOS, I do *not* experience this error; everything works fine - Using stripe-mock installed via cloning the repo and running...

@xavdid-stripe any ideas on this? Why would cloning the repo and using homebrew work fine, while the docker image apparently has old validation rules?

I wonder if this is due to #432… the [main dockerfile](https://github.com/stripe/stripe-mock/blob/e8c59fc2ed3837eeab89e0930f1f732b3e397f47/Dockerfile) includes a build step, while the [goreleaser dockerfile](https://github.com/stripe/stripe-mock/blob/e8c59fc2ed3837eeab89e0930f1f732b3e397f47/goreleaser.dockerfile) doesn’t… @richardm-stripe since you added #432, do you have any ideas...

Thanks…does somebody need to tag a new release though? I still see 0.186.0 from May 16 as the latest on [Docker Hub](https://hub.docker.com/r/stripe/stripe-mock/tags) and [GitHub](https://github.com/stripe/stripe-mock/releases)