ci(release): list every commit type in the changelog #2055

Merged

hckrman101 merged 1 commit from ci-changelog-all-types into main

2026-11-11 01:24:11 +00:00

hckrman101 commented

2026-11-11 01:23:42 +00:00

(Migrated from github.com)

rc.2's release notes list only the RDNA 1 fix, but three pull requests were merged since rc.1. release-please's default changelog shows only feat, fix, perf and revert, and treats every other type as not user-facing, so the build(release) pipeline list (#2044) and the test(display) fix (#2051) were left out.

This lists every Conventional Commit type in its own section (changelog-sections in release-please-config.json):

Type	Section
`feat`	Features
`fix`	Bug Fixes
`perf`	Performance Improvements
`revert`	Reverts
`refactor`	Code Refactoring
`build`	Build System
`ci`	Continuous Integration
`docs`	Documentation
`test`	Tests
`style`	Styles
`chore`	Miscellaneous Chores

Because release-please decides "user-facing" from the visible sections, a build, docs, ci, test, refactor, style or chore merge now also proposes the next release candidate (a patch-level bump, like fix). docs/versioning.md's table says so.

Commits whose title isn't a Conventional Commit are still not read; the PR-title check already requires one.

Once this merges, the open release PR (#2053) is regenerated and should list all three changes since rc.1. Untested on a real release-please run.

rc.2's release notes list only the RDNA 1 fix, but three pull requests were merged since rc.1. release-please's default changelog shows only `feat`, `fix`, `perf` and `revert`, and treats every other type as not user-facing, so the `build(release)` pipeline list (#2044) and the `test(display)` fix (#2051) were left out. This lists every Conventional Commit type in its own section (`changelog-sections` in `release-please-config.json`): | Type | Section | |---|---| | `feat` | Features | | `fix` | Bug Fixes | | `perf` | Performance Improvements | | `revert` | Reverts | | `refactor` | Code Refactoring | | `build` | Build System | | `ci` | Continuous Integration | | `docs` | Documentation | | `test` | Tests | | `style` | Styles | | `chore` | Miscellaneous Chores | Because release-please decides "user-facing" from the visible sections, a `build`, `docs`, `ci`, `test`, `refactor`, `style` or `chore` merge now also proposes the next release candidate (a patch-level bump, like `fix`). `docs/versioning.md`'s table says so. Commits whose title isn't a Conventional Commit are still not read; the PR-title check already requires one. Once this merges, the open release PR (#2053) is regenerated and should list all three changes since rc.1. Untested on a real release-please run.