Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Creating a custom version scheme (e.g. namespaced tags)
See original GitHub issueWe are currently using conventional-changelog “as is”, which means it creates version tags in the scheme of major.minor.patch, but in the current deployment pipeline we need to namespace/prefix the version number like so: frontend/customer-ui/1.2.3
I successfully changed the git tagging to the latter, but conventional-changelog still tries to compare un-namespaced versions 1.2.3.
Are the previousTag and currentTag options the key?
Can anyone give an advice on how to configure and use that?
Issue Analytics
- State:
- Created 7 years ago
- Comments:16 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@krnlde I have the same needs as you, and your problem can be solved by tagPrefix. But my problem is that the tag ‘1.3.0.20191226’ I defined is not a Semver Tag, which caused conventionalChangelog to be generated from the first commit. How to support custom tags? Or how to rewrite the comparison method?
Are there any further suggestions?