Really up to you and what your goals are, but ideally have at least working code and your envisioned public API implemented. I think it's fine to completely rew

Really up to you and what your goals are, but ideally have at least working code and your envisioned public API implemented. I think it's fine to completely rework your API based on feedback after putting it out there, but I wouldn't take a project very seriously if it got published while saying something along the lines of "oh I'm not sure yet if this is the right API" or if there's some giant, obvious gap of functionality missing. Personally, I prefer releasing when docs cover the public API and I have at least some test coverage.