commit-analyzer
commit-analyzer copied to clipboard
:bulb: semantic-release plugin to analyze commits with conventional-changelog
https://github.com/semantic-release/commit-analyzer#options > _npm package name_ of a custom conventional-changelog preset. i.e "conventional-changelog-conventionalcommits"? - Am I correct in understanding this 'name' would be the same value as used in the following...
- What type of object(s) does this option expect? Strings? Arrays? Please provide examples. > Note: For presets that expects a configuration object, such as [`conventionalcommits`](https://github.com/conventional-changelog/conventional-changelog/tree/master/packages/conventional-changelog-conventionalcommits), the `presetConfig` option must...
Current: https://github.com/conventional-changelog/conventional-changelog-config-spec/blob/master/versions/2.0.0/README.md Latest: https://github.com/conventional-changelog/conventional-changelog-config-spec/blob/master/versions/2.1.0/README.md
I've added to @semantic-release/commit-analyzer plugin a list of types under releaseRules: ``` module.exports = { branches: [ '+([0-9])?(.{+([0-9]),x}).x', 'main', 'dev', 'master' ], plugins: [ ["@semantic-release/commit-analyzer", { preset: "angular", releaseRules: [...
The following construct results in a wrong prerelease version and thus a failing job, as the tag already exists. **Steps to reproduce**: 1. `master` tagged `v1.0.0`, fast forwarded from `develop`...
So if someone does a `feat` commit and then a `BREAKING CHANGE` commit, then there will be a `major` version. However, what if someone makes a commit that says `BREAKING...
I have a package which is based upon a parent package. If parent is `x.y.z` and the child package is `a.b.c`, I would like to enforce `x.y` == `a.b`. I...
Perhaps this is already possible but after reading through the source code and checking the various dependencies I can't quite see a way of doing it. I would like to...
See https://github.com/favoloso/conventional-changelog-emoji/issues/20#issuecomment-606773923 I wanted to use `semantic-release` together with the linked package, but unfortunately, it's not working out of the box, I rather need to define all the release rules...
I'm trying to use semantic-release but I want my previous release to be a pre-release (`v2.0.0-alpha.1`). This tag already exists (no other tags exist). When running semantic-release, the next inferred...