chore(deps): update dependency conventional-changelog-conventionalcommits to v10

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
conventional-changelog-conventionalcommits (source)	^9.1.0 → ^10.0.0

---

Release Notes

conventional-changelog/conventional-changelog (conventional-changelog-conventionalcommits)

v10.2.1

Compare Source

Bug Fixes

• point package homepages and docs to documentation website (04796e2)

v10.2.0

Compare Source

Features

• support changelog preamble partial (#​1491) (e93dbe4)

v10.1.0

Compare Source

Features

• support changelog preamble (#​1489) (7d9794f)

v10.0.0

Compare Source

⚠ BREAKING CHANGES

• the commit type effect property replaces the hidden commit type property and the bumpStrict preset option for controlling changelog visibility and version bumps.

Fixes #​1476.

• Handlebars template strings and partial files were replaced with render functions.
• packages now require Node.js 22 or newer.

Features

• replace handlebars templates with render functions (#​1477) (55e6716)
• require node 22 (de5e136)
• support commit type effects (#​1484) (78761ae)

Bug Fixes

• encode compare URL tags (#​1483) (96bf235)
• render non-closing references separately (#​1482) (adb2c69)
• sort notes without compare-func (#​1487) (dc78285)

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "before 9am on Monday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[dawsontoth]

⚠️ CI is green but this silently breaks release notes. Please hold this one.

conventional-changelog-conventionalcommits v10 replaced Handlebars templates with render functions:

BREAKING CHANGES

• Handlebars template strings and partial files were replaced with render functions.
• the commit type effect property replaces the hidden commit type property and the bumpStrict preset option
• packages now require Node.js 22 or newer.

That new preset shape needs conventional-changelog-writer@9, but @semantic-release/release-notes-generator@14.1.1 — the latest published version — still pins conventional-changelog-writer: ^8.0.0. There is currently no release-notes-generator that can consume the v10 preset.

Reproduction

I ran the repo's own .releaserc.json presetConfig through generateNotes with a fixed set of four commits (feat, fix, perf, chore(deps)), on main vs this branch — identical script, identical commits:

main (preset v9) — all configured sections render:

### Features
* **codegen:** add new emitter (aaaaaaa)
### Bug Fixes
* correct nullable handling (bbbbbbb)
### Performance Improvements
* speed up parse (ddddddd)
### Dependency Updates
* **deps:** bump dprint (ccccccc)

This branch (preset v10.2.1) — only the header, every section silently dropped:

## [1.1.0](https://github.com/HarperFast/schema-codegen/compare/v1.0.0...v1.1.0) (2026-07-27)

	Features	Bug Fixes	Perf	Dependency Updates
v9 (main)	✅	✅	✅	✅
v10 (this PR)	❌	❌	❌	❌

Nothing in CI covers changelog rendering, which is why all 10 checks pass. If this merges, the next release ships an empty CHANGELOG entry and empty GitHub release notes.

Suggested disposition

Hold until @semantic-release/release-notes-generator ships a major that depends on conventional-changelog-writer@^9 and the v10 preset. Adding a Renovate rule to keep this preset on v9 until then would prevent the PR from being re-raised:

{
  "matchPackageNames": ["conventional-changelog-conventionalcommits"],
  "allowedVersions": "<10"
}

Good news: our presetConfig only uses { type, section } entries — no hidden or bumpStrict — so once the generator catches up this should be a clean bump with no config migration.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 10.x releases. But if you manually upgrade to 10.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.