conventional-recommended-version
Advanced tools
Determine the semantic version number of your project
Using a conventional-changelog commit history, determine the current version number of your project.
This is done by reading your local git commit history and searching for fixes, features, and breaking changes.
npm install conventional-recommended-version
import { getVersion } from 'conventional-recommended-version';
getVersion('/Users/you/projects/some-project').then(console.log);
// { major: 1, minor: 0, patch: 0 }
conventional-recommended-version currently only supports the angular conventional-changelog convention as that's the one I use.
Patches are welcome.
FAQs
Determine the semantic version number of your project
The npm package conventional-recommended-version receives a total of 4 weekly downloads. As such, conventional-recommended-version popularity was classified as not popular.
We found that conventional-recommended-version demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Ransomware negotiators share how modern cybercriminals operate like corporations, using specialized teams, negotiation tactics, and reputation management.
Security News
PyPI confirms no security flaws were exploited in the Ultralytics supply chain attack and highlights improvements for safer package publishing.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.