-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commits duplicate under new release versions in CHANGELOG.md #86
Comments
You can use |
I tried
Thoughts? |
I'm sorry, I meant https://github.com/release-it/release-it?tab=readme-ov-file#troubleshooting--debugging |
Based on the details you provided on SO, it seems you have disabled git tagging. Without git tags and a reference point for analyzing the commits, everything since the beginning of your repository's commits will be included. As a workaround, one need to provide the commit SHA or reference from the last changelog entries. Here’s how you can do that: const LAST_COMMIT_REF = "80e627c";
module.exports = {
plugins: {
'@release-it/conventional-changelog': {
infile: 'CHANGELOG.md',
preset: 'conventionalcommits',
type: [
{ "type": "feat","section": "Features" },
{ "type": "fix", "section": "Bug Fixes" }
],
gitRawCommitsOpts: {
from: LAST_COMMIT_REF
},
commitsOpts: {
from: LAST_COMMIT_REF,
},
}
}
} |
Did a detailed writeup here.
https://stackoverflow.com/questions/78196255/get-release-it-to-put-each-new-commit-under-the-corresponding-release-version-in
This is what is happening:
When the
CHANGELOG.md
is regenerated with new version numbers, previous commits are also rendered under the new version number, in addition to being rendered where they were previously.The text was updated successfully, but these errors were encountered: