Description
Describe the bug
I have a few new changes on my main branch. To test those changes, I create a pre-release with a tag like v1.2.3-next.0. This all works out great and the changelog is updated accordingly with the new pre-release.
After testing, I am happy with the changes and want to create a full release.
The problem that I see now is that the release changelog entry does not include changes, that were in my earlier pre-release even though they are not fully released yet.
Current behavior
The changelog does not take changes from pre-release into account for the next full release.
Expected behavior
Changes that were only in previous pre-releases should be included in the next full release since that is the release where they are first in a fully versioned release with a correct version number.
Environment
standard-versionversion(s): 9.3.1- Node/npm version: Node 14
- OS: Ubuntu 20.04
Possible Solution
I don't have one yet, but it's probably a rather easy fix to take the correct last full release instead of the last pre-release to start tracking changes.
Additional context
I set up a testing repo here
The behaviour can be observed on the releases page, e.g. Pre-Release v0.14.3-next.2 with the following Release v0.14.3 not having any changes noted in the changelog.