Discussion about releasing version 1

[ts-web]

Currently the @react-email/components library is at 0.0.31 and it should be upgraded/retagged to 1.0.0.

Having a 0.x version causes issues with semver expressions like ^ and it's not a good practice. If I use the package and I need to upgrade it in the future, I want to use semver to tell me whether the changes were major or not. Using a 0.x version number sidesteps all of this and basically there's no semver meaning in it at all.

If the reasoning is that this library is beta, semver has other mechanisms for that: prerelease versions. Besides, no matter whether you want to call it beta or not, it's a publicly released library, so in a sense it's not beta anymore.

If the reasoning is that this library is volatile and likely to change, the answer is still to release 1.0.0 now and just make the version 2.0.0 when there's a breaking change. It's the right thing to do. What is the alternative -- to pretend there isn't a breaking change and release 0.0.32. Do you want to be sentimental with the version number and stay on version 1.x as long as possible? When talk about this reasoning it all turns out to be not that important.

Is there another reason to stay 0.x?

If not, then given the issues with 0.x, can we set the version number to 1.0.0?

[gabrielmfern]

We're already thinking about this for some time, and we also dislike having them as 0.x. Going for 1.0 is definitely the way to go, but we're actually dropping the multiple packages for the next major release to unifying them all into react-email so this problem should go away very soon.

Thank you for the discussion either way.