Skip to content

PUBLISH.md

Latest commit

 

History

History
44 lines (29 loc) · 1.22 KB

PUBLISH.md

File metadata and controls

44 lines (29 loc) · 1.22 KB

Publishing

  1. Create a branch to stage the release, for example release-3.4.5 (Read semver to determine what type of version bump to use.)
git checkout -b release-3.4.5
git fetch
git reset --hard origin/master

  1. Run make storybook and verify that there are no regressions with Link.

  2. Update CHANGELOG.md with changes that will be included in the release, commit and push to the release branch.

  3. When ready, publish the new version from the branch before merging

make release-(patch|minor|major)
  1. Merge the branch

Manually publish to NPM

If make release-* from above errors out with an authentication issue, you may need to npm login or otherwise manually set up your ~/.npmrc file to make sure you have access to publish to npm.

Once you have done that, the following command will publish the latest version (already bumped and pushed in step 4) to the NPM registry:

  1. Publish to npm manually
npm --registry=https://registry.npmjs.com publish
  1. Push tags manually
git push --follow-tags

Also, under github releases page, draft a new release corresponding to the tag of the latest version.