Keep using npm to clean up dist-tags after a stable release

- After deploy, `yarn tag` gets prompted for login, because npm login != yarn login
- When I tried to do it locally, `yarn tag remove thelounge next` consistently gave me a 404, but `npm dist-tag rm thelounge next` worked nbd.
This commit is contained in:
Jérémie Astori 2019-01-27 17:54:58 -05:00 committed by GitHub
parent eec6ce80ae
commit 7ebdb84a30
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -63,5 +63,5 @@ deploy:
# If the current release is a stable release, remove potential pre-release tag
after_deploy: |
if [ "$(npm_dist_tag)" == "latest" ]; then
yarn tag remove thelounge next || true
npm dist-tag rm thelounge next || true
fi