Commit range does not use the previous tag to generate release notes
Running np --no-publish does not use the previous tag to generate changelog
Description
I am using np to create new versions of my app. However, when a new release is created the commit range always starts from 1.0.1
> np --no-publish
Publish a new version of app (current: 1.2.1)
Commits:
- Merge pull request #90 from zkootie/hotfix/add_version_scripts 6190aa0
- feat: updated entitlements for Apple signin e7747bf
- 1.2.1 865a1ea
- fix: workflow fix 4a7b052
- 1.2.0 cc9f777
- ...
- Feature/add apple signin (#56) 6adfe56
- Main (#55) b9aed25
- ...
- Merge pull request #50 from xxxx/main c97749d
- 1.0.2 baa80f6
Commit Range:
1.0.1...main
Expected behavior
Commit Ranage should start from 1.2.1
Environment
np - 10.0.7
Node.js - v18.19.0
npm - 10.2.3
Git - 2.38.1
OS - MacOS Sonoma
sindresorhus / np
A better `npm publish`
7.6k
How does funding with Polar work?
1
Pay now to fund the work behind this issue.
2
Get updates on progress being made.
3
Maintainer is rewarded once the issue is completed.
FAQ
Backer
You're funding impactful open source efforts
Contributor
You want to contribute to this effort
Maintainer
You want to get funding like this too