`preset: conventionalcommits` produces empty release notes with conventional-changelog-conventionalcommits v10

[dlecan]

With preset: "conventionalcommits", upgrading conventional-changelog-conventionalcommits to v10 makes generateNotes emit only the version header

Every section (Features, Bug Fixes, BREAKING CHANGES, …) disappears
Version detection in @semantic-release/commit-analyzer is unaffected, so a release is still triggered but ships an empty CHANGELOG / GitHub Release

Repro (offline, no git/network needed)

import { generateNotes } from "@semantic-release/release-notes-generator";
const c = (hash, message) => ({ hash, message, committerDate: "2026-06-27T00:00:00Z" });
const ctx = {
  commits: [c("aaaaaaa","feat: a"), c("bbbbbbb","fix: b")],
  lastRelease: { gitTag: "v1.0.0" },
  nextRelease: { version: "1.1.0", gitTag: "v1.1.0", type: "minor" },
  options: { repositoryUrl: "https://github.com/o/r" },
  cwd: process.cwd(), env: {}, logger: { log(){}, error(){} },
};
console.log(await generateNotes({ preset: "conventionalcommits" }, ctx));
// v9.x → renders ### Features / ### Bug Fixes
// v10.x → only "## [1.1.0](…)" header

Versions: release-notes-generator 14.1.1, conventional-changelog-conventionalcommits 10.2.0, node 22.

[travi]

same problem as semantic-release/commit-analyzer#921

[dlecan]

Workaround until release-notes-generator moves to `conventional-changelog-writer@9: force the writer with a package-manager override.

pnpm-workspace.yaml (or pnpm.overrides in package.json):

overrides:
  conventional-changelog-writer: ^9.2.0

[travi]

no, as mentioned in #992 (comment), the proper resolution to this is to avoid upgrading your dependency on conventional-changelog-conventionalcommits to v10 until the semantic-release ecosystem has been upgraded to support it