chore(master): release git-raw-commits 4.0.0

[github-actions]

🤖 I have created a release beep boop

4.0.0 (2023-08-26)

⚠ BREAKING CHANGES

• Node >= 16 is required

Features

• drop node 14 support (#1085) (1bce036)
• git-raw-commits: add support for multiple paths (#1079) (107daf2)
• git-raw-commits: ignore commits by regex (#1063) (47033e6)

Bug Fixes

• deps: update dependency dargs to v8 (#1028) (1dbcc99)
• deps: update dependency split2 to v4 (#1032) (d16ccc5)
• fix semver vulnerability (#1071) (3f5c99d), closes #1019

---

This PR was generated with Release Please. See documentation.

[coveralls]

coverage: 89.53%. remained the same when pulling db57fdd on release-please--branches--master--components--git-raw-commits into 9c138ee on master.

[github-actions]

🤖 Release is at https://github.com/conventional-changelog/conventional-changelog/releases/tag/git-raw-commits-v4.0.0 🌻

[Nazim-hasan]

Not working as expected flagged --commit-path=[''./path1', './../path2'] but not generating as expected.

[dangreen]

@Nazim-hasan Please try --path './path1' --path './../path2'

[Nazim-hasan]

@dangreen if I use conventional-changelog -p angular -i CHANGELOG.md -s --path path-1' --path 'path-2' doesn't ' Generate a changelog scoped to a specific directory'. It takes all the commits from all directories.

[dangreen]

@Nazim-hasan If you are using conventional-changelog cli tool then try --commit-path instead of --path

[Nazim-hasan]

@coveralls I'm using the npm run script and tried --commit-path and the passing string('path1') is working as expected. If I pass array or (--commit-path path-1 --commit-path path-2) It takes all the commits from all directories.

[dangreen]

@Nazim-hasan Fill free to create PR with a fix 👍