It is time to make a official release 1.0 for once. Then follow semver guidelines of course

[icazemier]

I updated to v0.14.2 just the other day, which added the default option forbidUnknownValues: true (totally agree!), see: #2196

But this library is here for ages already and this was really a breaking change on the major version "0" 😉.

So my suggestion is, bump to a new major, and be done with it, lets go to 1.0 right?

[braaar]

This breaking change should have bumped us to 0.15.0 as per the conventions of SemVer version 0, so that was a mistake in versioning, but still not the most egregious fault since version 0 of SemVer is generally considered unstable.

Let's move to #1775 for a discussion of the overall project progression and goals.

[icazemier]

You are correct, my mistake 😅.

Version 0 is considered "unstable", and therefor not a reason to bump to a new major in case of a breaking change according to semver.

But you (and this library) deserve this, this library is used by the millions!

And just to mention a rather popular library is promoting these NestJS