Valid commit message subject is rejected

[xmlking]

Expected Behavior

Subject starts with 1.0.1 should be considered valid

Current Behavior

printf "chore(release): 1.0.1 [skip ci]\n\n## 1.0.1 (2018-09-09)\n\n\n### Bug Fixes\n\n* build: now updating version (2d913ea)\n\n\n\n" | npx commitlint

This give error
Also reported here:
semantic-release/semantic-release#928 (comment)

Affected packages

• cli
• core
• prompt
• config-angular

Possible Solution

Steps to Reproduce (for bugs)

https://github.com/xmlking/ngx-starter-kit/blob/master/package.json

commitlint.config.js

```js ```

Context

Your Environment

Executable	Version
commitlint --version	VERSION
git --version	VERSION
node --version	VERSION

[byCedric]

So basically you are saying that @commitlint/config-conventional shouldn't enforce any subject casing, because it simply isn't in the spec right? Got the same issue using:

$ printf "chore(release): 1.0.1 [skip ci]\n\n## [1.0.1](https://github.com/xmlking/ngx-starter-kit/compare/v1.0.0...v1.0.1) (2018-09-09)\n\n\n### Bug Fixes\n\n* **build:** now updating version ([2d913ea](https://github.com/xmlking/ngx-s
tarter-kit/commit/2d913ea))\n\n\n\n" | npx commitlint -x '@commitlint/config-conventional'

I'm not sure if this was intentional, but it looks like the sentence-case setting of the subject-case rule is failing with numbers/semantic versioning.

Until this is resolved, you can temporarily work around this by adjusting the subject-sentence rule.

{
  "commitlint": {
    "extends": ["@commitlint/config-conventional"],
    "rules": {
      "subject-case": [2, "never", ["start-case", "pascal-case", "upper-case"]]
    }
  }
}

[marionebl]

@byCedric is right, we should ignore characters not matching [a-zA-Z] from the case rules in general.

[xmlking]

any update in this issue ?
thanks

[byCedric]

@xmlking Sorry, I had a bit too much work on my hands these past weeks. Right now, I'm writing a fix for this. Please stick with us here! 😄