Search Results for "tagging"

The conventional-changelog repo is managed as a monorepo; it's composed of many npm packages. It's recommended you use the high-level standard-version library, which is a drop-in replacement for npm's version command, handling automated version bumping, tagging, and CHANGELOG generation. Alternatively, if you'd like to move towards completely automating your release process as an output from CI/CD, consider using semantic-release. 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. ...