Comparing version 4.1.0 to 4.1.1
{ | ||
"name": "semver", | ||
"version": "4.1.0", | ||
"version": "4.1.1", | ||
"description": "The semantic version parser used by npm.", | ||
@@ -5,0 +5,0 @@ "main": "semver.js", |
@@ -19,8 +19,8 @@ semver(1) -- The semantic versioner for npm | ||
Usage: semver <version> [<version> [...]] [-r <range> | -i <inc> | -d <dec>] | ||
Usage: semver <version> [<version> [...]] [-r <range> | -i <inc> | --preid <identifier> | -l | -rv] | ||
Test if version(s) satisfy the supplied range(s), and sort them. | ||
Multiple versions or ranges may be supplied, unless increment | ||
or decrement options are specified. In that case, only a single | ||
version may be used, and it is incremented by the specified level | ||
option is specified. In that case, only a single version may | ||
be used, and it is incremented by the specified level | ||
@@ -105,2 +105,26 @@ Program exits successfully if any valid version satisfies | ||
#### Prerelease Identifiers | ||
The method `.inc` takes an additional `identifier` string argument that | ||
will append the value of the string as a prerelease identifier: | ||
````javascript | ||
> semver.inc('1.2.3', 'pre', 'beta') | ||
'1.2.4-beta.0' | ||
``` | ||
command-line example: | ||
```shell | ||
$ semver 1.2.3 -i prerelease --preid beta | ||
1.2.4-beta.0 | ||
``` | ||
Which then can be used to increment further: | ||
```shell | ||
$ semver 1.2.4-beta.0 -i prerelease | ||
1.2.4-beta.1 | ||
``` | ||
### Advanced Range Syntax | ||
@@ -166,4 +190,2 @@ | ||
Note: this is the same as the `~>` operator in rubygems. | ||
#### Caret Ranges `^1.2.3` `^0.2.5` `^0.0.4` | ||
@@ -170,0 +192,0 @@ |
Sorry, the diff of this file is not supported yet
Sorry, the diff of this file is not supported yet
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
New author
Supply chain riskA new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
298
120740
1