For now, the chan-cli and chan-core packages use an hardcoded release/tag prefix v. Used for tagging release & gh-release.
Some company or person may need to handle the version tagging with another or no prefix.
This PR intend to allow anybody to choose another prefix by using a new configuration named --release-prefix.
🔢 To Review
Steps to review the PR:
chan release
use the new --release-prefix
the resulting CHANGELOG.md file must use the chosen prefix
chan gh-release
use the new --release-prefix
the github redirection should use the chosen prefix
chanrc, chanrc.json, package.json
add the new config key release-prefix into one of chanrc, chanrc.json, package.json
when using both chan release or chan gh-release the release must be prefixed with the configured value
💬 Describe the pull request
For now, the
chan-cli
andchan-core
packages use an hardcoded release/tag prefixv
. Used for tagging release & gh-release. Some company or person may need to handle the version tagging with another or no prefix.This PR intend to allow anybody to choose another prefix by using a new configuration named
--release-prefix
.🔢 To Review
Steps to review the PR:
chan release
--release-prefix
CHANGELOG.md
file must use the chosen prefixchan gh-release
--release-prefix
chanrc
,chanrc.json
,package.json
release-prefix
into one ofchanrc
,chanrc.json
,package.json
chan release
orchan gh-release
the release must be prefixed with the configured value