semantic-release 20.1.1 → 20.1.3

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.
@@ -6,8 +6,8 @@
6
6
  const semanticRelease = require("semantic-release");
7
7
  const { WritableStreamBuffer } = require("stream-buffers");
8
8
 
9
- const stdoutBuffer = WritableStreamBuffer();
10
- const stderrBuffer = WritableStreamBuffer();
9
+ const stdoutBuffer = new WritableStreamBuffer();
10
+ const stderrBuffer = new WritableStreamBuffer();
11
11
 
12
12
  try {
13
13
  const result = await semanticRelease(
@@ -14,7 +14,7 @@ See our [Node Support Policy](node-support-policy.md) for our long-term promise
14
14
  The recommended approach is to run the `semantic-release` command from a CI job running on the latest available LTS version of node.
15
15
  This can either be a job used by your project to test on the latest Node LTS version or a dedicated job for the release steps.
16
16
 
17
- See [CI configuration](../usage/ci-configuration.md) and [CI configuration recipes](../recipes/release-workflow/README.md#ci-configurations) for more details.
17
+ See [CI configuration](../usage/ci-configuration.md) and [CI configuration recipes](../recipes/ci-configurations/README.md#ci-configurations) for more details.
18
18
 
19
19
  ## Alternative solutions
20
20
 
@@ -14,7 +14,7 @@ Here are a few examples of the CI services that can be used to achieve this:
14
14
  - [Wercker Workflows](http://devcenter.wercker.com/docs/workflows)
15
15
  - [GoCD Pipelines](https://docs.gocd.org/current/introduction/concepts_in_go.html#pipeline).
16
16
 
17
- See [CI configuration recipes](../recipes/ci-configurations#ci-configurations) for more details.
17
+ See [CI configuration recipes](../recipes/ci-configurations/README.md) for more details.
18
18
 
19
19
  ## Authentication
20
20
 
@@ -45,6 +45,6 @@ See each plugin's documentation for the environment variables required.
45
45
 
46
46
  The authentication token/credentials have to be made available in the CI service via environment variables.
47
47
 
48
- See [CI configuration recipes](../recipes/ci-configurations#ci-configurations) for more details on how to configure environment variables in your CI service.
48
+ See [CI configuration recipes](../recipes/ci-configurations/README.md) for more details on how to configure environment variables in your CI service.
49
49
 
50
50
  **Note**: The environment variables `GH_TOKEN`, `GITHUB_TOKEN`, `GL_TOKEN` and `GITLAB_TOKEN` can be used for both the Git authentication and the API authentication required by [@semantic-release/github](https://github.com/semantic-release/github) and [@semantic-release/gitlab](https://github.com/semantic-release/gitlab).
package/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "semantic-release",
3
3
  "description": "Automated semver compliant package publishing",
4
- "version": "20.1.1",
4
+ "version": "20.1.3",
5
5
  "type": "module",
6
6
  "author": "Stephan Bönnemann <stephan@boennemann.me> (http://boennemann.me)",
7
7
  "ava": {
@@ -57,11 +57,11 @@
57
57
  },
58
58
  "devDependencies": {
59
59
  "ava": "5.2.0",
60
- "c8": "7.12.0",
60
+ "c8": "7.13.0",
61
61
  "clear-module": "4.1.2",
62
62
  "codecov": "3.8.3",
63
63
  "delay": "5.0.0",
64
- "dockerode": "3.3.4",
64
+ "dockerode": "3.3.5",
65
65
  "file-url": "^4.0.0",
66
66
  "fs-extra": "^11.0.0",
67
67
  "got": "^12.5.0",
@@ -70,10 +70,10 @@
70
70
  "nock": "13.3.0",
71
71
  "p-retry": "^5.1.1",
72
72
  "prettier": "^2.7.1",
73
- "sinon": "15.0.1",
73
+ "sinon": "15.0.2",
74
74
  "stream-buffers": "3.0.2",
75
75
  "tempy": "^3.0.0",
76
- "testdouble": "3.16.8"
76
+ "testdouble": "3.17.0"
77
77
  },
78
78
  "engines": {
79
79
  "node": ">=18"