Skip to content

Latest commit

 

History

History
51 lines (36 loc) · 2.14 KB

CONTRIBUTING.md

File metadata and controls

51 lines (36 loc) · 2.14 KB

Release Checklist

Some unfortunately non-automated tasks that need to be done manually:

  1. Run yarn test and yarn test:dom in the top level dir and make sure jest + mocha browser tests are passing (you'll need to check mocha tests in the browser)
  2. Run yarn format-and-fix in the top level dir
  3. Make sure readme is up-to-date
  4. Verify that no unintended deps were added to dependencies in either package.json.

Beta versions for testing

Sometimes, you will want to test out changes before publishing them widely. In that case, do a pre-release by following these steps:

  1. npm version prepatch | preminor | premajor

  2. npm publish --tag beta

Real release

  1. Release flip-toolkit:
  • increment version number
  • run yarn build
  • commit with message formatted like: git commit -m '[email protected]'
  • run npm publish

Then, wait a bit (30mins+) and ensure the correct version shows up on:

  1. Once everything looks good, release react-flip-toolkit:
  • yarn upgrade flip-toolkit@^XXX
  • increment version number
  • run yarn build
  • commit with message formatted like: git commit -m '[email protected]'
  • run npm publish

Once again, verify that everything looks good: