feat(release): add conventional commits configurability for version and changelog

[fahslaj]

Current Behavior

• nx release version will only use feat and fix commit types when determining the specifier (when specifierSource is conventional-commits). It will also always assume that fixes are patches and feats are minor bumps.
• nx release changelog will only include feat, fix, and perf changes in changelogs.

Expected Behavior

• nx release version will consider user configuration when picking the specifier when specifierSource is conventional-commits.
• nx release changelog will consider user configuration when filtering commits to appear in the changelog. It will also consider the configured section title.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Mar 13, 2024 7:34pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 777c361. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --target=e2e --base=73a8091b9353538085c29ff7082514d138f1c72c --head=777c361ee5b7441dc41523228792229bc1bc363f --parallel=1
• nx affected --targets=lint,test,build --base=73a8091b9353538085c29ff7082514d138f1c72c --head=777c361ee5b7441dc41523228792229bc1bc363f --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=73a8091b9353538085c29ff7082514d138f1c72c --head=777c361ee5b7441dc41523228792229bc1bc363f
• nx documentation --no-dte
• nx affected -t e2e-macos --parallel=1 --base=73a8091b9353538085c29ff7082514d138f1c72c --head=777c361ee5b7441dc41523228792229bc1bc363f

---

Sent with 💌 from NxCloud.

[JamesHenry]

I'd like it to be made clearer that this is an advanced case and that most folks are perfectly fine/happy with the default behavior and no configuration should be required for most people (i.e. should just be "conventionalCommits": true

[fahslaj]

I can add something about this being an advanced use case, but I want to point out that the release.conventionalCommits property they are setting here is different than the existing release.version.conventionalCommits property that is frequently set to true to enable it for versioning. Most users will never set release.conventionalCommits, as its only valid value is an advanced config option outlined in this doc. It is invalid (and meaningless) for release.conventionalCommits to be set to true.

The reason there are two different properties is because this new one affects both version and changelog commands, so it didn't make sense to extend the existing release.version.conventionalCommits property to accept a configuration object.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.