pnpm release fails due to release commit message not conforming to conventional commit

[mrloop]

See cli output here

➜  ember-lottie git:(main) pnpm release

> [email protected] release /home/ewan/projects/qonto/ember-lottie
> release-it


🚀 Let's release ember-lottie (1.0.0...1.0.1)


Changelog:
## [1.0.1](https://github.com/qonto/ember-lottie/compare/v1.0.0...v1.0.1) (2023-12-19)

### Bug Fixes
* dont pass undefined options to fetch ([78e36d4](https://github.com/qonto/ember-lottie/commit/78e36d44e152679c6a5d8d0974576995243eaf20))
* update broken lockfile ([786b705](https://github.com/qonto/ember-lottie/commit/786b7057320ef398566edf63933272a412ad907c))


Changeset:
 M CHANGELOG.md
 M ember-lottie/package.json
 M package.json
 M test-app/package.json

? Commit (Release 1.0.1)? Yes
ERROR Error: ╭──────────────────────────────────────╮
│ 🥊 lefthook v1.5.5  hook: commit-msg │
╰──────────────────────────────────────╯
┃  commitlint ❯

⧗   input: Release 1.0.1
✖   subject may not be empty [subject-empty]
✖   type may not be empty [type-empty]

✖   found 2 problems, 0 warnings
ⓘ   Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint


exit status 1
  ────────────────────────────────────
summary: (done in 0.60 seconds)
🥊  commitlint
Rolling back changes...
Resetting local changes made
 ELIFECYCLE  Command failed with exit code 1.

[mrloop]

Does #333 fix this? Can this issue be closed? @michelegera

[michelegera]

Does #333 fix this? Can this issue be closed? @michelegera

Indeed it does 🙂
Now releases are delegated to the CI, and the release commit message conforms to CC standards. Closing this!