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.3.1 → 10.4.0

---

Release Notes

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

v10.4.0

Compare Source

Features

• fail loudly when a preset is rendered by an old writer (#​1539) (341e3f0), closes #​1495

v10.3.0

Compare Source

Features

• format references in breaking change notes (#​1529) (a8ef1ed), closes #​631
• group notes by their keyword (#​1533) (7be33d4), closes #​815

Bug Fixes

• use current host url paths (#​1534) (612d368), closes #​986

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 Europe/Sofia)

• Branch creation
  • "before 6am 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.

[azlekov]

Holding this open rather than merging — the v10 bump can't be adopted yet, and the breaking change can't be resolved in .releaserc.js.

Why: v10 rewrites the preset onto conventional-changelog's new render-function writer API (conventional-changelog-writer@9 / @conventional-changelog/template) and replaces the hidden type property + bumpStrict with effect. But semantic-release's release-notes-generator@14 and commit-analyzer@13 still bundle the Handlebars-based conventional-changelog-writer@8, which cannot consume the v10 preset.

Verified in an isolated install of our exact toolchain:

Preset	config	release notes
9.3.1 (current)	hidden: false/true	✅ renders ### ✨ Features …
10.0.0	hidden: …	❌ empty (header only)
10.0.0	effect: 'bump'/'hidden' (correct v10)	❌ still empty

The writer silently drops every commit from the changelog/release notes — no error, CI stays green, releases just get blank notes. No published @semantic-release/release-notes-generator depends on writer@9 yet (latest 14.1.1 and beta both pin writer@^8).

Next step: revisit once @semantic-release/release-notes-generator ships a release built on conventional-changelog-writer@^9. Until then this update is a no-go regardless of config.

[azlekov]

Re-checked against v10.3.0 (2026-08-10). Still a hard blocker — nothing upstream has moved.

Tracked upstream

• preset: conventionalcommits produces empty release notes with conventional-changelog-conventionalcommits v10 semantic-release/release-notes-generator#992 — "preset: conventionalcommits produces empty release notes with conventional-changelog-conventionalcommits v10" (open, filed 2026-06-28)
• Upgrade conventionalcommits preset to v10 semantic-release/commit-analyzer#921 — "Upgrade conventionalcommits preset to v10" (open, same root cause per maintainer)

Maintainer guidance in #992 is exactly our stance: do not upgrade your own dependency on conventional-changelog-conventionalcommits to v10 until the semantic-release ecosystem supports it. A conventional-changelog-writer: ^9 package-manager override was proposed in that thread and explicitly rejected by the maintainer as the wrong resolution — so that is not a shortcut we should take either.

Why it still fails

v10 only emits the new render-function writer API (@conventional-changelog/template); semantic-release still bundles the Handlebars writer:

Package (latest published)	conventional-changelog-writer
@semantic-release/release-notes-generator@14.1.1	^8.0.0
@semantic-release/release-notes-generator@14.0.0-beta.1	^8.0.0
@semantic-release/commit-analyzer@13.0.1	^8.0.0
@semantic-release/commit-analyzer@14.0.0-beta.2 (2026-08-07)	^8.0.0, and it pins conventional-changelog-conventionalcommits: ^9.0.0

conventional-changelog-writer@9.2.1 has been out since 2026-08-10, but no semantic-release plugin — stable or beta — depends on it. The newest commit-analyzer beta actually hard-pins the preset back to v9, so upstream is not mid-migration on this.

Re-verified with our exact toolchain

Isolated install of @semantic-release/release-notes-generator@14.1.1 (resolved conventional-changelog-writer@8.4.0) + preset 10.3.0, three synthetic commits (feat(cli), fix(daemon), chore(deps)), our real presetConfig:

Preset	config	release notes
10.3.0	hidden	❌ header only — 2 lines
10.3.0	effect: 'bump'/'hidden' (correct v10)	❌ header only — 2 lines
10.3.0	no presetConfig	❌ header only — 2 lines
9.3.1 (control)	hidden	✅ ### ✨ Features + ### 🐛 Bug Fixes

Same failure mode as before: no throw, no warning, exit 0 — the release just ships blank notes, and on main a blank CHANGELOG.md entry with it. Rewriting .releaserc.js to effect does not help, because the writer never gets far enough to read it.

Revisit trigger

@semantic-release/release-notes-generator and @semantic-release/commit-analyzer both shipping on conventional-changelog-writer@^9. Watch the 14.x betas of both — commit-analyzer's beta line is where the ^9 preset pin currently lives.

Holding this PR open. Same hold applied to the sibling PRs in dodi-smart/dirahq-cloud#7, dodi-smart/kodni.me#96 and dodi-smart/infrasensing-supabase-platform#53.