Detect breaking changes

[kenn]

Is your feature request related to a problem? Please describe.

When I read the list of breaking changes, I have a hard time figuring out if I’m affected or not.

https://github.com/stripe/stripe-node/releases/tag/v18.0.0

Describe the solution you'd like

What if the library offered a CLI command to check if your codebase is using any of the breaking APIs? Even better—a codemod for those changes?

When I started using Stripe in the early days, it wasn’t this complicated. Now the library feels increasingly bloated, especially for simple use cases like ours.

Describe alternatives you've considered

Paddle

Additional context

No response

[jar-stripe]

Hi @kenn , thanks for writing in and thank you for the feedback! These are great ideas, and very much in line with some discussions we've been having internally. Let me take this back to the team; I can't promise any kind of timeline but we are definitely receptive to ways to make it easy to upgrade our SDKs and understand the impact of the upgrade.

Can you share a bit more about your use case? And, was there something specific in the list of changes you were looking for or had a hard time finding or teasing out that I can help you with?