semantic-release-lerna 2.13.0 → 2.14.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (3) hide show
  1. package/README.md +10 -3
  2. package/dist/index.js +3050 -494
  3. package/package.json +4 -3
package/README.md CHANGED
@@ -2,8 +2,6 @@
2
2
 
3
3
  [**semantic-release**](https://github.com/semantic-release/semantic-release) plugin to publish lerna managed [npm](https://github.com/lerna/lerna) packages to [npm](https://www.npmjs.com).
4
4
 
5
- This is WORK-IN-PROGRESS so there will most likely be bugs and it as only really been tested under the narrow use-cases I myself need it for.
6
-
7
5
  It is intended to be a drop-in replacement of the `@semantic-release/npm` plugin.
8
6
 
9
7
  The plugin works in the following way:
@@ -43,7 +41,16 @@ If a package version is bumped all the packages depending (`dependencies`, `devD
43
41
  $ npm install semantic-release-lerna -D
44
42
  ```
45
43
 
46
- ## Usage
44
+ ## Configuration
45
+
46
+ ### npm registry authentication
47
+
48
+ When publishing to the [official registry](https://registry.npmjs.org/), it is recommended to use [trusted publishing](https://docs.npmjs.com/trusted-publishers) for authentication.
49
+ See the [npm registry authentication](https://github.com/semantic-release/npm?tab=readme-ov-file#npm-registry-authentication) section for `@semantic-release/npm` for details.
50
+
51
+ For alternative registries or when trusted publishing cannot be used the `NPM_TOKEN` environment variable must be set.
52
+
53
+ ### semantic release configuration
47
54
 
48
55
  The plugin can be configured in the [**semantic-release** configuration file](https://github.com/semantic-release/semantic-release/blob/master/docs/usage/configuration.md#configuration):
49
56