We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running np --no-publish does not use the previous tag to generate changelog
np --no-publish
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
> 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
Commit Ranage should start from 1.2.1
np - 10.0.7 Node.js - v18.19.0 npm - 10.2.3 Git - 2.38.1 OS - MacOS Sonoma
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Running
np --no-publish
does not use the previous tag to generate changelogDescription
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.1Expected 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
The text was updated successfully, but these errors were encountered: