Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`lerna-changelog` always combines `Unreleased` with the previous release.
See original GitHub issueI noticed that lerna-changelog always combines the latest release with the Unreleased code together to Unreleased. So the previous version disappears from the generated changelog. Is this a known issue? Is there a way to change this?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
The chronicles of semantic-release and monorepos
Since semantic-release and lerna appeared, the community has made several attempts to combine these technologies together.
Read more >@latiwesh/conventional-changelog-core NPM | npm.io
How many releases of changelog you want to generate. It counts from the upcoming release. Useful when you forgot to generate any previous...
Read more >@lerna/version | Yarn - Package Manager
Automatic loading of .env files in lerna run with the new task-runner implementation. By default the modern task runner powered by Nx will...
Read more >@stem/lerna - npm Package Health Analysis | Snyk
An important project maintenance signal to consider for @stem/lerna is that it hasn't seen any new versions released to npm in the past...
Read more >Configuration Options - Renovate Docs
Renovate always uses the config from the repository's default branch, ... need to add another step after Renovate before you can release a...
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 Free
Top 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
hmm, not sure what you mean. the workflow is usually to run
lerna-changelogbefore bumping the version number. haven’t had any issues like what you described yet when doing it that way.@Turbo87 I think this has been happening to us in ember-data too