rules skipped if commit message contains '/'

The below release rules works well, until the commit message has a '/' in it.
For ex BUGFIX-RELEASE: wait to set up event emitter until calling /process
Here are the logs in this case:

[9:47:58 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
328[9:47:58 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: BUGFIX-RELEASE: wait to set up event emitter until calling /process (#15)
329
330* wait to set up event emitter until calling /process
334* add tests
335
336* small fixes
3372020-05-21T21:47:58.969Z semantic-release:commit-analyzer Analyzing with custom rules
3382020-05-21T21:47:58.971Z semantic-release:commit-analyzer Analyzing with default rules
339[9:47:58 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release

My release rules looks like this:

 ["@semantic-release/commit-analyzer", {
        "preset": "eslint",
        "releaseRules": [
        {
          "subject": "*",
          "release": false
        },
        {
          "subject": "FEATURE-RELEASE:*",
          "release": "minor"
        },
        {
          "subject": "BUGFIX-RELEASE:*",
          "release": "patch"
        },
        {
          "subject": "BREAKING-RELEASE:*",
          "release": "major"
        }
        ]
      }]

Start by reproducing the issue with the provided releaseRules and the commit subject containing /process, then compare it with a subject that has no slash. The fix is complete when the BUGFIX-RELEASE rule reliably produces a patch release for the reported commit, with coverage for the slash case.