Gar

I think coupling to the internals is probably not the best idea. We can't remove the regex exports without a semver-breaking change otherwise I'd advocate to do so. Ideally the...

https://github.com/npm/node-semver/pull/334

Looks like the discussion answered this as well as it can be answered.

We're being extra judicious in accepting breaking changes at this point. I am going to close this due to age and lack of any other issues showing that this is...

The `npm@10` roadmap does have plans to stop auto-correcting package.json entries. However we will always have to account for the fact that packuments in existing tarballs have this data.

That said, this is not a bug per se w/ this module but with npm itself. Folks using this package can get whatever behavior they want, either cleaning it or...

I think it's worth exploring a way to make valid choose between v1 and v2. Docs would probably end up being part of that PR right?

https://github.com/npm/node-semver/pull/532

This has been rebased and the commit rewritten to conform to conventional commit syntax. Is this something we still want?

npm does not use loose checking when validating semver for publishing. It calls `semver.clean` which in this PR still returns `null` (which would cause npm to refuse to publish) ```javascript...