You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i apparently misremembered the default behavior of npm pubilsh when you are publishing a package with a semver pre-release version. if something is a pre-release and there are stable releases, we should tag the npm publish as next, not latest. you can see examples of this with prettier and eslint
The text was updated successfully, but these errors were encountered:
per conversation in #1054 (comment)
i apparently misremembered the default behavior of npm pubilsh when you are publishing a package with a semver pre-release version. if something is a pre-release and there are stable releases, we should tag the npm publish as next, not latest. you can see examples of this with prettier and eslint
The text was updated successfully, but these errors were encountered: