From 571274dea11070870f7d9f61ff3e94ef3103794c Mon Sep 17 00:00:00 2001
From: nweajoseph <82170925+nweajoseph@users.noreply.github.com>
Date: Thu, 15 Sep 2022 15:15:10 -0700
Subject: [PATCH] fix: "no release" is the lowest priority

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} // <----- this should NOT override 'patch'
]
```

would skip the release matching commits, even though another rule matches them with a higher release value. that is to say: this commit codifies `false` or `null` release values as the "lowest" release value, making it possible to treat "no release" the same way we treat all other release values, instead of treating it as a special exception. the primary use-case for this change is more granular control over commit analysis when using `scope`s
---
 lib/default-release-types.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/default-release-types.js b/lib/default-release-types.js
index 937b01a0..4ef997c9 100644
--- a/lib/default-release-types.js
+++ b/lib/default-release-types.js
@@ -3,4 +3,4 @@
  *
  * @type {Array}
  */
-module.exports = ['major', 'premajor', 'minor', 'preminor', 'patch', 'prepatch', 'prerelease'];
+module.exports = ['major', 'premajor', 'minor', 'preminor', 'patch', 'prepatch', 'prerelease', false, null];