We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(NOTE: This issue has been replicated from the old repository)
If the latest version is v1.0.0. If the commit from v1.0.0 is not cloned down, then conventional tools will try to release v0.0.1.
The correct tag should be released, it should be at least more than the most recent tag.
It is releasing version 0.0.1
0.0.1
Notice an error is thrown
› Error: Command failed with exit code 128: git tag v0.0.1 › fatal: tag 'v0.0.1' already exist
A workaround it to do a full clone when releasing. For github actions that will be the below
steps: - name: Checkout uses: actions/checkout@v3 with: fetch-depth: 0
git clone --depth 1 https://github.com/Practically/webpack-config
cd webpack-config
git fetch --tags
export CT_TOKEN=xxx
conventional-tools release-semver
The text was updated successfully, but these errors were encountered:
No branches or pull requests
(NOTE: This issue has been replicated from the old repository)
Description
If the latest version is v1.0.0. If the commit from v1.0.0 is not cloned down, then conventional tools will try to release v0.0.1.
Expected Behaviour
The correct tag should be released, it should be at least more than the most recent tag.
Actual Behaviour
It is releasing version
0.0.1Notice an error is thrown
A workaround it to do a full clone when releasing. For github actions that will be the below
Steps to Reproduce the Problem
git clone --depth 1 https://github.com/Practically/webpack-configcd webpack-configgit fetch --tagsexport CT_TOKEN=xxxconventional-tools release-semverThe text was updated successfully, but these errors were encountered: