• Add @types/conventional-commits-parser to resolve TS7016 error
• Dependency added to both @commitlint/cli and @commitlint/rules packages

Add missing TypeScript types for conventional-commits-parser

• Added @types/conventional-commits-parser version ^5.0.2 to devDependencies

@commitlint/cli/package.json

Add missing TypeScript types for conventional-commits-parser

• Added @types/conventional-commits-parser version ^5.0.2 to devDependencies

@commitlint/rules/package.json

Description

@types/conventional-commits-parser is added only to @commitlint/cli/@commitlint/rules, while
@commitlint/types and @commitlint/parse also import conventional-commits-parser types and
publish .d.ts files. This makes builds and consumer typing resolution depend on monorepo hoisting
rather than explicit package dependencies, which can break in focused/isolated installs and for
downstream TS users.

Code

@commitlint/cli/package.json[44]

+    "@types/conventional-commits-parser": "^5.0.2",

Evidence

The repo publishes declaration files from @commitlint/types and @commitlint/parse and those
declarations are derived from source that directly imports conventional-commits-parser types; yet
those packages do not declare @types/conventional-commits-parser. The PR adds the @types package
only in other workspaces, so @commitlint/types/@commitlint/parse will only succeed if the
dependency is hoisted into a shared node_modules, which is not guaranteed under focused installs /
stricter workspace setups.

@commitlint/cli/package.json[41-50]
@commitlint/types/package.json[1-10]
@commitlint/types/src/parse.ts[1-6]
@commitlint/types/package.json[31-37]
@commitlint/parse/package.json[1-10]
@commitlint/parse/src/index.ts[1-7]
@commitlint/parse/package.json[38-46]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`@commitlint/types` and `@commitlint/parse` import types from `conventional-commits-parser` and publish `.d.ts` files, but they do not declare `@types/conventional-commits-parser`. The PR adds the types package only to other workspaces, which makes type resolution depend on workspace hoisting and can break in focused/isolated installs and for downstream TS consumers.

### Issue Context
- `@commitlint/types` exports types referencing `conventional-commits-parser`.
- `@commitlint/parse` exports a function whose signature uses `Commit`/`ParserOptions` from `conventional-commits-parser`.

### Fix Focus Areas
- @commitlint/types/package.json[31-38]
- @commitlint/parse/package.json[38-47]
- @commitlint/types/src/parse.ts[1-6]
- @commitlint/parse/src/index.ts[1-7]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Description

The repo uses conventional-commits-parser ^6.2.1 but the PR adds
@types/conventional-commits-parser ^5.0.2. This may be fine, but the major-version mismatch
should be verified to avoid incorrect typings or future typecheck breakage.

Code

@commitlint/rules/package.json[R42-45]

+    "@types/conventional-commits-parser": "^5.0.2",
    "conventional-changelog-angular": "^8.1.0",
    "conventional-commits-parser": "^6.2.1",
    "glob": "^11.0.0"

Evidence

The PR introduces a v5 @types/* package alongside a v6 runtime dependency. Even if this compiles
today, it’s a risk area: type definitions could be out of sync with the installed library’s API
surface.

@commitlint/rules/package.json[38-46]
@commitlint/types/package.json[31-34]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
There is a major-version mismatch between the runtime library (`conventional-commits-parser@^6.2.1`) and the added type package (`@types/conventional-commits-parser@^5.0.2`). This could cause subtle type inaccuracies or future typecheck failures.

### Issue Context
The mismatch is introduced by the PR dependency addition.

### Fix Focus Areas
- @commitlint/rules/package.json[38-46]
- @commitlint/cli/package.json[41-48]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools