commit-analyzer

commit-analyzer copied to clipboard

This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/semantic-release/commit-analyzer). > [!NOTE] These dependencies have not received...

renovate[bot]

release: false should be the lowest priority rule

2

Consider what happens when we expand [this test](https://github.com/semantic-release/commit-analyzer/blob/master/test/analyze-commit.test.js#L110) to apply `scope`: ```js test('Return "false" for release type ONLY if the matching rule has no higher "release"', (t) => { const...

nweajoseph

prior to this commit, using a custom analysis rule that set release to `false`, for example: ``` [ {type: 'fix', scope: 'frontend', release: 'patch'}, {type: 'fix', scope: '*', release: false}...

nweajoseph

Hello, I am doing some tests when merging a prerelease branch for example `develop `into a release branch for example `main`, I was expecting that after the release of a...

arkadioz

Use the standard `conventional-changelog-preset-loader` to load presets

1

I think using `conventional-changelog-preset-loader` should be the best solution for #589 and reduce the burden on the `@semantic-release/commit-analyzer` maintainer. Import loadPreset function from the package and use it to load...

1aron

Providing a PR description breaks custom releaseRules

1

Hi all, my intention is to release a new patch version when the commit message doesn't start with `fix:` or `feat:`. These custom `releaseRules` work, **except** when the PR contains...

MBR41

Use RegExp instead of micromatch.

3

Micromatch is more geared towards path matching and that doesn't really play well with e.g. Bitbucket style pull request messages like this example: > Pull request #323: feature/SMKY-1231 Responsiveness fixes...

kontza

How do I add a releaseRule that also respects the `!` for a breaking change? (conventionalcommits preset)

5

We’re using the `conventionalcommits` preset. In this preset, adding an exclamation after the type triggers a breaking change/major version bump. Using the default `releaseRules` this works. `feat!:`, `fix!:` and `perf!:`...

natesilva

The `analyzeCommits` plugin configuration is invalid. Your configuration for the analyzeCommits plugin is ``.

1

Hello, I'm trying to get this plugin working, however I'm always running into the error What I tried so far was the .releaserc.json and package.json config types with both having...

mklueh

Incorrect JSDoc Type

1

The return type of `analyzeCommits` is declared as `String|null` in the JSDoc header. However, `analyzeCommits` is an async function. Return type should be `Promise` instead. https://github.com/semantic-release/commit-analyzer/blob/685f65ad82eae5e6d627b5812d4031c2a63f02aa/index.js#L12-L26

GravlLift