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
Historically, the default pre-release phase was hardcoded to "alpha". As stated in the README, this resulted in a default version of 0.0.0-alpha.0.{height} or a post-RTM version of {major}.{minor}.{patch+1}-alpha.0.{height}. E.g. the next commit after a 1.0.0 tag would be versioned 1.0.1-alpha.0.1.
This feature introduces a new option for the default pre-release phase. For example, the option may be set to "preview":
This will result in a default version of 0.0.0-preview.0.{height} or a post-RTM version of {major}.{minor}.{patch+1}-preview.0.{height}. E.g. the next commit after a 1.0.0 tag would be versioned 1.0.1-preview.0.1.
The text was updated successfully, but these errors were encountered:
Outcome of #242, raised by @Selmirrrrr.
Historically, the default pre-release phase was hardcoded to "alpha". As stated in the README, this resulted in a default version of
0.0.0-alpha.0.{height}
or a post-RTM version of{major}.{minor}.{patch+1}-alpha.0.{height}
. E.g. the next commit after a1.0.0
tag would be versioned1.0.1-alpha.0.1
.This feature introduces a new option for the default pre-release phase. For example, the option may be set to "preview":
This will result in a default version of
0.0.0-preview.0.{height}
or a post-RTM version of{major}.{minor}.{patch+1}-preview.0.{height}
. E.g. the next commit after a1.0.0
tag would be versioned1.0.1-preview.0.1
.The text was updated successfully, but these errors were encountered: