Mark prereleases with next tag and recommended stable version with latest tag
As mentioned in the Release Policy section of the README, prerelease versions (after 1.0.0) will be marked with the next
dist-tag so the npm client won't prefer the prerelease over a stable version.
To adhere to this policy, we need to modify our release process so prereleases (alpha, beta, and rc releases) for the next major release are detected and appropriately flagged with the dist-tag next
.
If the dist-tag is not set, it defaults to latest
.
Edited by Dan Allen