什么是git-semver-tags，Get all git semver tags of your repository in reverse chronological order
Having problems? want to contribute? join our community slack.
Generate a CHANGELOG from git metadata
It’s recommended you use the high level standard-version library, which handles the entire tagging and CHANGELOG generation process.
Alternatively, the conventional-changelog-cli allows you to generate a CHANGELOG from the command line.
About this Repo
The conventional-changelog repo is managed as a monorepo; it’s composed of many npm packages.
conventional-changelog/conventional-changelog API repo can be found in packages/conventional-changelog.
Plugins Supporting Conventional Changelog
Modules Important to Conventional Changelog Ecosystem
- conventional-changelog-cli - the full-featured command line interface
- standard-changelog - command line interface for the angular commit format.
- conventional-github-releaser - Make a new GitHub release from git metadata
- conventional-recommended-bump - Get a recommended version bump based on conventional commits
- conventional-commits-detector - Detect what commit message convention your repository is using
- commitizen - Simple commit conventions for internet citizens.
- commitlint - Lint commit messages
Node Support Policy
We only support Long-Term Support versions of Node.
We specifically limit our support to LTS versions of Node, not because this package won’t work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment.
It’s possible this package will work correctly on newer versions of Node. It may even be possible to use this package on older versions of Node, though that’s more unlikely as we’ll make every effort to take advantage of features available in the oldest LTS version we support.
As each Node LTS version reaches its end-of-life we will remove that version from the
engines property of our package’s
package.json file. Removing a Node version is considered a breaking change and will entail the publishing of a new major version of this package. We will not accept any requests to support an end-of-life version of Node. Any merge requests or issues supporting an end-of-life version of Node will be closed.
We will accept code that allows this package to run on newer, non-LTS, versions of Node. Furthermore, we will attempt to ensure our own changes work on the latest version of Node. To help in that commitment, our continuous integration setup runs against all LTS versions of Node in addition the most recent Node release; called current.
engines property. If you encounter issues installing this package, please report the issue to your package manager.