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
No response
Adding semantic versioning helps determine a version and release that version over npm registry as well.
Use npm package named npm install @semantic-release/changelog @semantic-release/git -D This will be dev dependencies.
npm install @semantic-release/changelog @semantic-release/git -D
Commit messages should be properly written otherwise it the automation will not understand and may release higher or lower package version.
The text was updated successfully, but these errors were encountered:
Hey @Gauravdarkslayer, Thanks for contributing and Congrats on opening Issue 🎉
We will try to review as soon as possible and a maintainer will get back to you soon!
Sorry, something went wrong.
No branches or pull requests
Start Date
No response
Implementation PR
No response
Reference Issues
No response
Summary
Adding semantic versioning helps determine a version and release that version over npm registry as well.
Basic Example
Use npm package named
npm install @semantic-release/changelog @semantic-release/git -D
This will be dev dependencies.
Drawbacks
Commit messages should be properly written otherwise it the automation will not understand and may release higher or lower package version.
Unresolved questions
No response
The text was updated successfully, but these errors were encountered: