Stripe API Version table in README is years outdated

[happycappie]

Existing Issue or Pull Request Verification

• Confirmed, no existing Issues or Pull Requests found related to my submission.

Package Version

3.1.1

Are you using the latest version?

• Yes, I verified the issue is still present in the latest version.

Steps to Reproduce

Compare the table in Which version should I use to the list at Stripe API versions.

Expected Result

Mapping of :stripity_stripe versions to Stripe API versions after 2019-10-17:

• 2023-10-16
• 2023-08-16
• 2022-11-15
• 2022-08-01
• 2020-08-27
• 2020-03-02
• 2019-12-03
• 2019-11-05

Actual Result

[yordis]

the generator stopped working #829

We need some consensus in terms of what I should do to fix it!

[github-actions]

This issue has been automatically marked as "stale:discard". If this issue still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment.

[PJUllrich]

The OpenAPI spec you use for code generation has the latest API version in info -> version. Could you maybe update the Readme with it?

I see it in spec3.json -> "info" -> "version"

[github-actions]

This issue has been automatically marked as "stale:discard". If this issue still relevant, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment.

[happycappie]

bump, please see comment above from #831 (comment)

[yordis]

Related to #829

[sygour]

Hello,

I wanted to update the lib to the latest version but hit the same issue.
Then I found that in the source, the version is already available:

• https://github.com/beam-community/stripity-stripe/blob/v3.2.0/lib/stripe/api.ex#L19

Can we rely on this version?

If so, could we at least add it to the README as a workaround?

[alolis]

I am a little bit confused as to what is happening with this library because it seems that it's using a very old stripe api version and the generator seems broken for some time. Am I missing something?

[yordis]

I’m not the original author of this package. I stepped in to maintain it after it had been abandoned because I didn’t want to see the Elixir community left without a Stripe SDK.

The way the SDK was originally built relied on a few assumptions that no longer hold true. Addressing this now requires very specialized handling to avoid introducing breaking changes.

If you follow the linked discussions and PRs, you’ll see there’s a significant amount of work involved. I’m happy to help you explore other alternatives if that would be more practical.

As an alternative, here’s a blog post that demonstrates a different approach to integrating with Stripe https://dashbit.co/blog/sdks-with-req-stripe

---

I’ve spent a lot of time trying to bring the Elixir ecosystem in line with what’s common in other languages like Go, Java, Node, PHP, Ruby, C#, C++, and Rust—where code generation is the standard and expected practice. Unfortunately, I wasn’t able to gain much traction. Things became even more challenging when some community leaders actively pushed against codegen SDKs. While I understand some of their concerns, the reality is that most of the industry expects generated SDKs, and Elixir remains an exception. You can participate at erlef/libs-and-frameworks#2 My intent was to move (maybe) everything to leverage the https://github.com/OpenAPITools/openapi-generator package since it is what most companies use it so it would make it easier to provide "official" SDKs.

I don’t mind contributing unpaid work, I done it for more than a decade, but the lack of support—and, at times, even additional friction in finding the right resources—has made it extremely difficult to move things forward. I’ve done my best to help, support, and build alignment, but without broader backing, there’s only so much I can do.

I am burned out from open source, and seeking alignment.

At this point, my recommendation would be to reach out to consulting firms or organizations that can dedicate the resources needed to take on this workload and move the project forward.

[alolis]

Hey @yordis ! Thanks for replying and apologies for my delay! I like the approach the original author has taken (thin wrappers + code generation) so I gave it a go the other day to manually bring the lib to a more latest Stripe API version (specifically 2025-08-27.basil).

I do not know if it will help others or if you want to check it out and merge it to main, but you can have a look here if you want and if you like it, I can open a merge request.

It needed a couple small changes in the Phases.Compile module but nothing crazy. I run the tests and there are 12 that failing but from the looks of it nothing worrying. Didn't fix them because I only wanted to make a test with the library and see if it actually works. Seems to work, but obviously a more experienced person with the library needs to have a look.

I understand your frustration, personal health is always the highest priority! Do what's best for YOU :)