@nx/js:release-version
DO NOT INVOKE DIRECTLY WITH nx generate
. Use nx release version
instead.
Webinar April 17: Making the Argument for MonoreposWebinar April 17: Making the Argument for MonoreposRegister now!
Please do not extend this schema as it is part of Nx internal usage.
DO NOT INVOKE DIRECTLY WITH nx generate
. Use nx release version
instead.
1nx generate release-version ...
2
By default, Nx will search for release-version
in the default collection provisioned in workspace.json.
You can specify the collection explicitly as follows:
1nx g @nx/js:release-version ...
2
Show what will be generated without writing to disk:
1nx g release-version ... --dry-run
2
The ProjectGraphProjectNodes being versioned in the current execution.
ProjectGraph instance
The resolved release group configuration, including name, relevant to all projects in the current execution.
disk
registry
, disk
, git-tag
Which approach to use to determine the current version of the project.
{}
Additional metadata to pass to the current version resolver.
Additional arguments to pass to the package manager when updating the lock file with an install command.
Whether to ignore install lifecycle scripts when updating the lock file with an install command.
The optional prerelease identifier to apply to the version, in the case that the specifier argument has been set to prerelease.
The root directory of the directory (containing a manifest file at its root) to publish. Defaults to the project root
Exact version or semver keyword to apply to the selected release group. Overrides specifierSource.
prompt
prompt
, conventional-commits
Which approach to use to determine the semver specifier used to bump the version of the project.
Whether to skip updating the lock file after updating the version.