-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
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
fix(release): fix --first-release with conventional commits and independent projects #21320
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit ff3c89c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
f6b18b1
to
2c31b92
Compare
…endent projects (#21320)
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Current Behavior
nx release
tries to commit changes when there are changed files on disk, but no staged changes. This causes the commit git operation to error.nx release --first-release
fails on the first release for a repo configured with conventionalCommits: true and independent projects relationship. (The command still assumes a previous git tag exists)Expected Behavior
nx release
does not try to commit changes when there are no staged changes, regardless of other changes on disk.nx release --first-release
indicates to the version generator that it should not assume a previous git tag exists. Instead, the first git commit in the repo is used, which is consistent with the changelog behavior on the first release.