publish --conventional-commits Changelog not committed
See original GitHub issuelerna publish --conventional-commits
works well, but doesn’t fully commit everything- usually leaving a lingering changelog that I have to commit by hand after. It seems to commit some change logs but not all.
Expected Behavior
Should commit all changelogs
Current Behavior
Always leaves one changelog that I have to commit by hand (publishes others)
Possible Solution
Steps to Reproduce (for bugs)
- Make changes to a package and make sure lerna changed sees it
- Make a conventional commit
lerna publish --conventional-commits
- Observer there’s a changelog hanging around after the operation completes
lerna.json
{
"version": "independent",
"npmClient": "yarn",
"useWorkspaces": true,
"command": {
"version": {
"message": "chore(release): publish %s"
},
"publish": {
"conventionalCommits": true
}
},
"ignoreChanges": ["**/__fixtures__/**", "**/__tests__/**", "**/*.md"]
}
Context
I’m just trying to automate publishing versions and changelogs
Your Environment
Executable | Version |
---|---|
lerna --version |
3.13.2 |
npm --version |
6.9.0 |
yarn --version |
1.15.2 |
node --version |
10.15.3 |
OS | Version |
---|---|
NAME | VERSION |
macOS Sierra | 10.14.4 |
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Using "lerna publish --conventional-commits" auto generate ...
I use lerna publish --conventional-commits to auto generate CHANGELOG.md. And lerna default use "conventional-changelog-angular" preset ...
Read more >@lerna/conventional-commits | Yarn - Package Manager
Change Log. All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.
Read more >Automated Releases - Melos
If a commit message does not follow the Conventional Commits specification, it will be ignored. Filter out commits with types that don't trigger...
Read more >Contribution Releases | TinaCMS Docs
Generate CHANGELOGs and Git tags: lerna version \ --conventional-commits \ --conventional-prerelease \ --no-push \ --allow-branch next \ -m "chore(publish): ...
Read more >Conventional Commits
Additional types are not mandated by the Conventional Commits specification, and have no ... The description is a short summary of the code...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
After a bunch of tinkering, trial and error… I noticed that that a few or our changelog files were lowercase:
changelog.md
instead ofCHANGELOG.md
. Interestingly enough, it would put the change in that file, but not stage it to be committed I guess.I renamed it to be uppercase and everything is working! Thanks for jumping in here so quickly and trying to help!
Not that I’m aware of. I just renamed all my
changelog.md
files.