Skip to content

fix(release): align release-note sections with studio and guard preset at v9 - #45

Merged
dawsontoth merged 1 commit into
mainfrom
fix/release-notes-consistency
Jul 27, 2026
Merged

fix(release): align release-note sections with studio and guard preset at v9#45
dawsontoth merged 1 commit into
mainfrom
fix/release-notes-consistency

Conversation

@dawsontoth

Copy link
Copy Markdown
Contributor

Why

Our semantic-release repos generate GitHub release notes with the conventionalcommits preset, but the behavior had drifted and, in several repos, notes were coming out empty. Two separate causes:

  1. Preset v10 breaks rendering. @semantic-release/release-notes-generator@14 still bundles the Handlebars-based conventional-changelog-writer@8. The conventional-changelog-conventionalcommits v10 preset rewrote its templates as JS functions for the newer @conventional-changelog/template engine (writer@9); fed to writer@8 only the header survives, so every release note collapses to just its ## [x.y.z]… line.
  2. presetConfig.types drift. Types like chore/chore(deps)/ci/build/style were hidden or missing, so dependency-only releases (the common Renovate case) produced empty notes.

This PR makes the repo consistent with studio's canonical release config (which surfaces every commit type) and holds the preset on v9 where relevant. Reference: HarperFast/studio#1560.

What changed

  • Aligned .releaserc.json presetConfig.types to studio's superset (adds chore→Chores, build, ci, style; renames to match studio) so no release comes out empty.
  • Added the Renovate guard.

(No lockfile change — the preset devDep is already on a 9.x range, so notes already render; this is the consistency + guard piece.)

Canonical presetConfig.types (matches studio)

feat→Features, fix→Bug Fixes, perf→Performance Improvements, refactor→Refactoring, chore(deps)→Dependency Updates, chore→Chores, docs→Documentation, style→Styles, test→Tests, build→Build System, ci→Continuous Integration, revert→Reverts — nothing hidden, so no release comes out empty.

Renovate guard

Added a packageRules entry pinning conventional-changelog-conventionalcommits to <10 so Renovate won't re-introduce the v10 breakage. Remove once @semantic-release/release-notes-generator ships a writer@9-based major.

Verification

  • .releaserc.json is valid JSON.

🤖 Generated with Claude Code

…t at v9

- Aligned `.releaserc.json` `presetConfig.types` to studio's superset (adds `chore`→Chores, `build`, `ci`, `style`; renames to match studio) so no release comes out empty.
- Added the Renovate guard.

(No lockfile change — the preset devDep is already on a 9.x range, so notes already render; this is the consistency + guard piece.)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@dawsontoth
dawsontoth requested a review from a team as a code owner July 27, 2026 16:58

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the release configuration in .releaserc.json to refine commit types and sections, and adds a rule in renovate.json to pin conventional-changelog-conventionalcommits to versions below 10 to avoid compatibility issues. Feedback on .releaserc.json highlights that the conventionalcommits preset does not support a scope property within the types array. Consequently, the two conflicting chore entries will overwrite each other, and it is recommended to consolidate them into a single entry.

Comment thread .releaserc.json
@dawsontoth
dawsontoth merged commit a4d8236 into main Jul 27, 2026
9 checks passed
@dawsontoth
dawsontoth deleted the fix/release-notes-consistency branch July 27, 2026 17:20
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 1.1.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant