Skip to content

Commit 9ff595b

Browse files
committed
fix: change package scope to @progress
1 parent 4e42bab commit 9ff595b

File tree

4 files changed

+11
-11
lines changed

4 files changed

+11
-11
lines changed

README.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ This projects allows you to push prerelease package versions to NPM, hidden behi
66

77
## Prerequisites
88

9-
- semantic-release **4.x+**
9+
- semantic-release **6.x+**
1010
- git **2.13+** (used for tag parsing)
1111

1212
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.
1515

1616
1. Install the node module through the following command:
1717

18-
npm install --save-dev @telerik/semantic-prerelease
18+
npm install --save-dev @progress/semantic-prerelease
1919

2020
2. Describe the branches that will publish prerelease versions.
2121
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.
3434

3535
// package.json
3636
"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"
4242
}
4343

4444
4. Use `semantic-prerelease publish` instead of `npm publish` in the end of your build. This publishes the prerelease versions behind dist-tags.

bin/release-master

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ if [ $? -ne 0 ]; then
2121
exit 1
2222
fi
2323

24-
npm update @telerik/semantic-prerelease
24+
npm update @progress/semantic-prerelease
2525
./node_modules/.bin/semantic-prerelease --validate
2626
if [ $? -ne 0 ]; then
2727
"Semantic Prerelase not configured correctly. Aborting."

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"name": "@telerik/semantic-prerelease",
2+
"name": "@progress/semantic-prerelease",
33
"description": "A set of plug-ins for semantic-release that provide a workflow for prerelease versions.",
44
"repository": {
55
"type": "git",

validateConfig.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,8 +23,8 @@ function validateConfig(config) {
2323

2424
['analyzeCommits', 'getLastRelease', 'verifyConditions', 'verifyRelease']
2525
.forEach((plugin) => {
26-
assert(`Expected release.${ plugin } to be set to "@telerik/semantic-prerelease/${ plugin }"`, () =>
27-
release[plugin] == `@telerik/semantic-prerelease/${ plugin }`);
26+
assert(`Expected release.${ plugin } to be set to "@progress/semantic-prerelease/${ plugin }"`, () =>
27+
release[plugin] == `@progress/semantic-prerelease/${ plugin }`);
2828
});
2929

3030
if (!valid) {

0 commit comments

Comments
 (0)