You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be a good idea to have a script for publishing automatically a new version of the NPM package every a PR is merged against master. This script could run inside Jenkins and read NPM authorization data from environment variables or an environment file, hidden to git so we avoid security issues.
This script could contain the following commands:
# this updates the package version and creates a git tag automatically, as this documentation says:
# https://docs.npmjs.com/cli/version
npm run patch
npm run build
cd dist
# we can follow the instructions in this post for npm login to work here
# https://circleci.com/docs/1.0/npm-login/
echo -e "$NPM_USER\n$NPM_PASS\n$NPM_EMAIL" | npm login
npm publish
The text was updated successfully, but these errors were encountered:
It would be a good idea to have a script for publishing automatically a new version of the NPM package every a PR is merged against master. This script could run inside Jenkins and read NPM authorization data from environment variables or an environment file, hidden to git so we avoid security issues.
This script could contain the following commands:
The text was updated successfully, but these errors were encountered: