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
When configuring a requireBranch, it'd be nice if this key supported an object format that allowed you to specify multiple branches, but also information on whether that branch is a pre-release branch.
Therefore when release-it runs on the v2.1.0-alpha branch, it will always release pre-release semver types with the name alpha... v2.1.0-alpha.X
Currently, I believe any of this additional logic may need to be handled in a hook if not a direct plugin as it would need to overwrite the determined version in the bump logic.
When configuring a
requireBranch
, it'd be nice if this key supported an object format that allowed you to specify multiple branches, but also information on whether that branch is a pre-release branch.For example:
Therefore when
release-it
runs on thev2.1.0-alpha
branch, it will always releasepre-release
semver types with the namealpha
...v2.1.0-alpha.X
Currently, I believe any of this additional logic may need to be handled in a
hook
if not a directplugin
as it would need to overwrite the determined version in thebump
logic.Trying to find a solution similar to
semantic-release
pre-release branches.The text was updated successfully, but these errors were encountered: