fix(semver): range handling includes prerelease when it should not
A bug in the semver package caused prereleases to be included in version ranges by default. Prereleases, per the spec, are not expected to be API compatible with the releases themselves. The semver package now ignores prereleases when evaluating constraints when the constraint does not contain a prerelease. If the constraint contains a prerelease they are evaluated.
Showing
Please
register
or
sign in
to comment