changelog
changelog copied to clipboard
[Help] How do I get this to work at all?
in my package.json
"release": {
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/github",
"@semantic-release/git"
]
},
package versions:
$ cat package.json | jq ".devDependencies" | grep semantic
"@semantic-release/changelog": "^5.0.1",
"@semantic-release/git": "^9.0.0",
"semantic-release": "^17.0.7",
repo: https://github.com/NullVoxPopuli/ember-jsqr I manually created the change log
C.I. log: https://github.com/NullVoxPopuli/ember-jsqr/runs/702505043?check_suite_focus=true
What's happening:
- CHANGELOG.md is empty
What I expect
- CHANGELOG.md to be populated with all my releases and versions, and continue to update as I merge stuff
I just learned that, according to https://spectrum.chat/semantic-release/general/how-to-rebuild-changelog-from-scratch~347e02df-a8cb-4081-afce-1f4f3dfd908e, back-filling the changelog isn't supported.
I was able to backfill with:
npx standard-changelog --first-release
hopefully semantic-release adds to it
it doesn't look like standard-changelog is quite the same? look at this generation: https://github.com/NullVoxPopuli/ember-jsqr/blob/master/CHANGELOG.md#0910-2020-05-23 there is a giant header in between minor versions :-\
@NullVoxPopuli According to your CI logs , your commit didn't trigger a release because it was not one of (feat,fix), which is acutly the default commit message for triggering a new release, what i can see from your logs that your commit message was chore, thats why there was no new release triggered and no changelog file created.
Regarding the second question, yes thats weird i don't and seeing to tags 0.9.0 twice is definitely wrong, not sure why.
This feature seems clearly a missing piece of this plugin
We are just using npx conventional-changelog-cli -p angular -i .docs/src/changelog.md -s -r 0 in our ci pipeline
@NullVoxPopuli According to your CI logs , your commit didn't trigger a release because it was not one of (feat,fix).
@abdelrahmanahmed Even I tried with fix or feat commit messages which did generate a github release, but it didn't generate any CHANGELOG.md.
Please refer this sample repo of mine for config files: https://github.com/gouravkhator/temp-git/