@@ -6,7 +6,7 @@ This projects allows you to push prerelease package versions to NPM, hidden behi
6
6
7
7
## Prerequisites
8
8
9
- - semantic-release ** 4 .x+**
9
+ - semantic-release ** 6 .x+**
10
10
- git ** 2.13+** (used for tag parsing)
11
11
12
12
This project has been tested in Travis-CI and Jenkins builds.
@@ -15,7 +15,7 @@ This project has been tested in Travis-CI and Jenkins builds.
15
15
16
16
1 . Install the node module through the following command:
17
17
18
- npm install --save-dev @telerik /semantic-prerelease
18
+ npm install --save-dev @progress /semantic-prerelease
19
19
20
20
2 . Describe the branches that will publish prerelease versions.
21
21
In this example, commits in the ` develop ` branch pushes prerelease versions to the ` dev ` dist-tag. Use ` fallbackTags ` to bootstrap the versions.
@@ -34,11 +34,11 @@ This project has been tested in Travis-CI and Jenkins builds.
34
34
35
35
// package.json
36
36
"release": {
37
- "analyzeCommits": "@telerik /semantic-prerelease/analyzeCommits",
38
- "generateNotes": "@telerik /semantic-prerelease/generateNotes",
39
- "getLastRelease": "@telerik /semantic-prerelease/getLastRelease",
40
- "verifyConditions": "@telerik /semantic-prerelease/verifyConditions",
41
- "verifyRelease": "@telerik /semantic-prerelease/verifyRelease"
37
+ "analyzeCommits": "@progress /semantic-prerelease/analyzeCommits",
38
+ "generateNotes": "@progress /semantic-prerelease/generateNotes",
39
+ "getLastRelease": "@progress /semantic-prerelease/getLastRelease",
40
+ "verifyConditions": "@progress /semantic-prerelease/verifyConditions",
41
+ "verifyRelease": "@progress /semantic-prerelease/verifyRelease"
42
42
}
43
43
44
44
4 . Use ` semantic-prerelease publish ` instead of ` npm publish ` in the end of your build. This publishes the prerelease versions behind dist-tags.
0 commit comments