Skip to content

Commit 9cffff5

Browse files
committed
fix: don't include chore PRs in GH release page
This change adjusts the release-it config for both this repo, as well as what the create script generates, so that the previous changes to enhance the changelog generation flows through to the github release page too. I discussed this here release-it/release-it#1025 (comment), and @webpro theorized it was the autoGenerate that overrode the changelog output from being applied to the GH release too. I created a test repo to verify and confirmed that removing `autoGenerate`, indeed, fixed the issue: https://github.com/michaelfaith/mf-cta-testing/releases 2.0.2 is after this change, which included both a chore change and fix change, but changelog and GH release page only show the bug fix (notice also the group heading, which isn't in the previous releases). 2.0.1 is before the change, with the original configuration
1 parent fb3558f commit 9cffff5

File tree

2 files changed

+0
-2
lines changed

2 files changed

+0
-2
lines changed

.release-it.json

-1
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,6 @@
44
"requireCommits": true
55
},
66
"github": {
7-
"autoGenerate": true,
87
"release": true,
98
"releaseName": "v${version}"
109
},

src/blocks/blockReleaseIt.ts

-1
Original file line numberDiff line numberDiff line change
@@ -122,7 +122,6 @@ export const blockReleaseIt = base.createBlock({
122122
requireCommits: true,
123123
},
124124
github: {
125-
autoGenerate: true,
126125
release: true,
127126
releaseName: "v${version}",
128127
},

0 commit comments

Comments
 (0)