This package has version that is not compliant with semantic versioning. To be compliant with semantic versioning it should not have v prefix in package.json
For bug reports:
What went wrong? Integration with other tools fails. Namely patch-plugin when using yarn
What did you expect should have happened? It should have correct version so it would not introduce issues with integration with different tools
What was the config you used? -
What stacktrace or error message from your provider did you see? -
For feature proposals:
What is the use case that should be solved. The more detail you describe this in the easier it is to understand for us. -
If there is additional config how would it look -
Similar or dependent issues:
Additional Data
This step in publish workflow config of github actions seems to be an issue:
- name: Version
run: yarn version --new-version ${{ github.event.release.tag_name }} --no-git-tag-version --no-commit-hooks
It sets tag name as a version including prefix (v).
This is a Bug Report
Description
This package has version that is not compliant with semantic versioning. To be compliant with semantic versioning it should not have
vprefix inpackage.jsonFor bug reports:
patch-pluginwhen usingyarnFor feature proposals:
Similar or dependent issues:
Additional Data
This step in
publishworkflow config of github actions seems to be an issue:It sets tag name as a version including prefix (
v).Issue with more context about problem created by non semver compliant version number of this package: https://github.com/ds300/patch-package/issues/360