Semver is generating the same version
See original GitHub issueWe integrated continuous deployment on Nx Plugin ngx-deploy-npm and we’re using Semver and its postTargets feature to trigger the deployment.
For some reason, Semver generates the same version when there is nothing new, you can see it here -> https://github.com/bikecoders/ngx-deploy-npm/runs/4091615454?check_suite_focus=true
This causes an unwanted behavior and an error because the tag already exists on the repo.
✔ bumping version in ./packages/ngx-deploy-npm/package.json from 3.0.4 to 3.0.4
✔ outputting changes to ./packages/ngx-deploy-npm/CHANGELOG.md
✔ committing ./packages/ngx-deploy-npm/package.json and ./packages/ngx-deploy-npm/CHANGELOG.md and all staged files
✔ tagging release v3.0.4
fatal: tag 'v3.0.4' already exists
Command failed: git tag -a v3.0.4 -m chore(release): 3.0.4
fatal: tag 'v3.0.4' already exists
The weird thing is when I run this locally it has the expected behavior, do not generate a version

Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
Semantic Versioning 2.0.0 | Semantic Versioning
Semantic Versioning 2.0.0. Summary. Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes ...
Read more >How to behave if a project uses SemVer, but its maintainer is ...
Bootstrap uses semver, and bootstrap-sass maintains the same version number, but with the addition of the fourth number to specify ...
Read more >SemVer versioning: how we handled it with linear interval ...
SemVer versioning representation First, we need a generic representation of a semantic version to start with. We assume that a semantic version ......
Read more >Semantic Versioning and version number formats - Flownative
In an automated build and deployment pipeline you deal a lot with version numbers. At Flownative, we generally follow the rules of Semantic...
Read more >SemVer Considered Harmful | Joey Lynch's Site
Most packaging systems (deb, rpm, python, ruby, java, etc …) cannot simultaneously install multiple major versions of the same package name.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Been monitoring making use of
--base-branch. It worked alright for a few days. Seems that it’s back to giving use the error that tag already exists.@aderito7 I opened an issue for that, would love to see your contribution!