rename release-candidate.sh to release

docs/en/contributing-to-appium/release-appium.md

@@ -11,11 +11,11 @@ Appium follows the GitLab flow approach. Releases are made on release branches t
 
 ## Create a release candidate
 1. Checkout the release branch (e.g.: `git checkout releases/1.21 && git pull origin releases/1.21`)
-1. `bash ./scripts/release-candidate.sh rc`
+1. `bash ./scripts/release.sh rc`
 
 ## Publish to GA
 1. Checkout the release branch (e.g.: `git checkout releases/1.21 && git pull origin releases/1.21`)
-1. `bash ./scripts/release-candidate.sh latest`
+1. `bash ./scripts/release.sh latest`
 1. Update the site docs by going to https://github.com/appium/appium.io/pulls and merging the latest pull request that was opened by the Triager bot. Close any other pull requests opened by Triager bot.
 1. Create a new release on GitHub: go to `https://github.com/appium/appium/releases/tag/v<VERSION>` and hit "Edit Tag". Make the release name `<VERSION>` (e.g., `2.0.5`), then paste in the changelog (but not the changelog header for this version). If it's a beta release, mark as pre-release.
 1. Create a new post on discuss.appium.io announcing the release. Post it in the "News" category. Paste in the changelog and any choice comments. Pin it and unpin the previous release post.

scripts/release-branch.sh

@@ -10,4 +10,4 @@ git commit -m 'add shrinkwrap'
 echo "* npm version $1.0-rc.0"
 npm version $1.0-rc.0
 git push origin releases/$1
-bash ./scripts/release-candidate.sh
+bash ./scripts/release.sh

scripts/release-candidate.sh

@@ -1,4 +0,0 @@
-npm version prerelease --preid=$1
-git push
-git push --tags
-npm publish --tag $1