nweajoseph

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...

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}...