Skip to content

Commit

Permalink
fix: change package scope to @progress
Browse files Browse the repository at this point in the history
  • Loading branch information
tsvetomir committed Jun 2, 2022
1 parent 4e42bab commit 9ff595b
Show file tree
Hide file tree
Showing 4 changed files with 11 additions and 11 deletions.
14 changes: 7 additions & 7 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ This projects allows you to push prerelease package versions to NPM, hidden behi

## Prerequisites

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

This project has been tested in Travis-CI and Jenkins builds.
Expand All @@ -15,7 +15,7 @@ This project has been tested in Travis-CI and Jenkins builds.

1. Install the node module through the following command:

npm install --save-dev @telerik/semantic-prerelease
npm install --save-dev @progress/semantic-prerelease

2. Describe the branches that will publish prerelease versions.
In this example, commits in the `develop` branch pushes prerelease versions to the `dev` dist-tag. Use `fallbackTags` to bootstrap the versions.
Expand All @@ -34,11 +34,11 @@ This project has been tested in Travis-CI and Jenkins builds.

// package.json
"release": {
"analyzeCommits": "@telerik/semantic-prerelease/analyzeCommits",
"generateNotes": "@telerik/semantic-prerelease/generateNotes",
"getLastRelease": "@telerik/semantic-prerelease/getLastRelease",
"verifyConditions": "@telerik/semantic-prerelease/verifyConditions",
"verifyRelease": "@telerik/semantic-prerelease/verifyRelease"
"analyzeCommits": "@progress/semantic-prerelease/analyzeCommits",
"generateNotes": "@progress/semantic-prerelease/generateNotes",
"getLastRelease": "@progress/semantic-prerelease/getLastRelease",
"verifyConditions": "@progress/semantic-prerelease/verifyConditions",
"verifyRelease": "@progress/semantic-prerelease/verifyRelease"
}

4. Use `semantic-prerelease publish` instead of `npm publish` in the end of your build. This publishes the prerelease versions behind dist-tags.
Expand Down
2 changes: 1 addition & 1 deletion bin/release-master
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ if [ $? -ne 0 ]; then
exit 1
fi

npm update @telerik/semantic-prerelease
npm update @progress/semantic-prerelease
./node_modules/.bin/semantic-prerelease --validate
if [ $? -ne 0 ]; then
"Semantic Prerelase not configured correctly. Aborting."
Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"name": "@telerik/semantic-prerelease",
"name": "@progress/semantic-prerelease",
"description": "A set of plug-ins for semantic-release that provide a workflow for prerelease versions.",
"repository": {
"type": "git",
Expand Down
4 changes: 2 additions & 2 deletions validateConfig.js
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ function validateConfig(config) {

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

if (!valid) {
Expand Down

0 comments on commit 9ff595b

Please sign in to comment.