This package is published to NPM automatically by CircleCI when code is merged into the dev or master branches. To publish a new version, simply update the version in package.json and merge your code into the appropriate branch.
- The
devbranch will publish versions marked asalphaorbeta. - The
masterbranch will publish any version (alpha,beta, orlatest). In both cases, the code will only be published if the version number differs from the current version published under the respective dist tag.
If you need to publish a package manually, you can run the following commands from the root folder:
cd <template>
yarn publish:packageThe publishing script will look at the version in the package.json and automatically determine whether to publish an alpha, beta, or latest package.
For this command to work, you must have an NPM token configured in your environment variables or you can perform a login prior to executing the publish command via:
cd <template>
npm adduser && yarn publish:packagePublishing manually should only be done for
alphaorbetapackages. The command will work forlatestpackages, but this should be avoided except in rare situations where the automatic publishing functionality is not working in CircleCI.