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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Releasing as "prerelease" does not consider commit history.
@jscutlery/semver had the same issue until this February 馃槄 jscutlery/semver#688
@jscutlery/semver
x.y.z should for instance be bumped to (x+1).y.z-preid.0 if the commit history has a breaking change and the release specifier is "prerelease"
No response
nx release version ...
Node : 18.18.2 OS : darwin-arm64 pnpm : 8.10.0 nx : 18.3.3 @nx/js : 18.3.3 @nx/jest : 18.3.3 @nx/linter : 18.3.3 @nx/eslint : 18.3.3 @nx/workspace : 18.3.3 @nx/devkit : 18.3.3 @nx/eslint-plugin : 18.3.3 @nx/playwright : 18.3.3 @nx/plugin : 18.3.3 @nx/react : 18.3.3 @nrwl/tao : 18.3.3 @nx/vite : 18.3.3 @nx/web : 18.3.3 typescript : 5.4.2 --------------------------------------- Registered Plugins: @jnxplus/nx-maven ... --------------------------------------- Community plugins: @jnxplus/nx-maven : 0.42.1 @monodon/rust : 1.4.0 @ngx/deploy-npm : 7.1.0 @nx-go/nx-go : 3.0.0 @nx-tools/nx-container : 5.2.0 --------------------------------------- Local workspace plugins: ...
pnpm 8.10.0
The text was updated successfully, but these errors were encountered:
JamesHenry
No branches or pull requests
Current Behavior
Releasing as "prerelease" does not consider commit history.
@jscutlery/semver
had the same issue until this February 馃槄 jscutlery/semver#688Expected Behavior
x.y.z should for instance be bumped to (x+1).y.z-preid.0 if the commit history has a breaking change and the release specifier is "prerelease"
GitHub Repo
No response
Steps to Reproduce
nx release version ...
)Nx Report
Failure Logs
No response
Package Manager Version
pnpm 8.10.0
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: