Yeah that's pretty much what I had in mind.

I'd add further that more than likely once your API became something usable new use-cases and ideas came up. I wouldn't call major version numbers "failures" but "evolutions".

The context of your project changing over the years requiring breaking API changes is good and healthy.