Skip to content

Latest commit

 

History

History
25 lines (16 loc) · 1.21 KB

7. having-your-changes-published.md

File metadata and controls

25 lines (16 loc) · 1.21 KB
Raw

Contribution Guide

  1. Getting Set up
  2. Building Samples and Packages
  3. Running a Sample or Storybook
  4. Testing your changes
  5. Writing unit tests
  6. Submitting a PR
  7. Having your changes published

7. Having your changes published 🚀

Once your PR has completed your changes are ready to be published in a new version! We do manual publishes of new package versions semi-regularly, as well as alpha packages nightly. If you are looking to test your changes as soon as possible in your app we recommend installing the alpha version and verifying your changes before we release a new non-alpha version of the package.

New Version Release Cadence

We aim to publish new versions of the packages every 2-8 weeks once an appropriate alpha version has been fully tested.

Nightly alpha builds

We publish new alpha versions nightly to npm. These can be installed and tested as soon as they are published.