@dotcom-tool-kit/circleci-npm 1.7.0 → 1.8.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 (2) hide show
  1. package/package.json +5 -5
  2. package/readme.md +1 -1
package/package.json CHANGED
@@ -1,18 +1,18 @@
1
1
  {
2
2
  "name": "@dotcom-tool-kit/circleci-npm",
3
- "version": "1.7.0",
3
+ "version": "1.8.0",
4
4
  "description": "",
5
5
  "main": "lib",
6
6
  "scripts": {
7
- "test": "cd ../../ ; npx jest --silent --projects plugins/circleci-npm"
7
+ "test": "echo \"Error: no test specified\" && exit 1"
8
8
  },
9
9
  "keywords": [],
10
10
  "author": "FT.com Platforms Team <platforms-team.customer-products@ft.com>",
11
11
  "license": "ISC",
12
12
  "dependencies": {
13
- "@dotcom-tool-kit/types": "^1.7.0",
14
- "@dotcom-tool-kit/circleci": "^1.7.0",
15
- "@dotcom-tool-kit/npm": "^1.7.0"
13
+ "@dotcom-tool-kit/types": "^1.8.0",
14
+ "@dotcom-tool-kit/circleci": "^1.8.0",
15
+ "@dotcom-tool-kit/npm": "^1.8.0"
16
16
  },
17
17
  "repository": {
18
18
  "type": "git",
package/readme.md CHANGED
@@ -39,7 +39,7 @@ If you don't have the automated comment in your `config.yml` and therefore choos
39
39
  only: /^v\d+\.\d+\.\d+(-.+)?/
40
40
  ```
41
41
 
42
- The tool-kit/publish job is triggered in your circleci pipeline when your branch name matches the semver format eg. v1.6.0-beta.1 , v1.6.0. If your branch name is a beta version ie. v1.6.0-beta.1, then the publish job will tag your branch as a prerelease version. But if your branch name is a release version ie. v1.6.0, then the publish job will tag your branch as the latest version.
42
+ The tool-kit/publish job is triggered in your circleci pipeline once you do a release with a tag matching the semver format, e.g. `v1.6.0-beta.1`, `v1.6.0`. If your tag is a beta version, i.e. `v1.6.0-beta.1`, then the publish job will tag your build as a prerelease version. But if your tag is a release version, i.e. `v1.6.0`, then the publish job will tag your build as the latest version.
43
43
 
44
44
  ## Hooks
45
45