Skip to content

Latest commit

 

History

History
26 lines (14 loc) · 1.14 KB

RELEASING.md

File metadata and controls

26 lines (14 loc) · 1.14 KB
Raw

Releasing a new version of Primer Primitives

Prepare the release

The Primer Primitives release process is automated using Changesets and GitHub Actions.

  1. Visit the pull requests page and find the latest, open "release tracking" pull request from primer-css. If there isn't one, we'll need to build the next release by merging in PRs with changeset files.

Test the release candidate (GitHub staff only):

  1. Ensure test automation checks have completed and passed

  2. Install and smoke test the Release Candidate on at least one consumer application.

  3. Review the change log for accuracy and completeness.

Publish the release

  1. If the release PR is approved and you've done necessary testing, merge it.

    After additional CI checks finish, the docs site will be deployed and @primer/primitives will be published with your changes to the latest dist-tag. You can check npm to see if actions has finished.

  2. You're done 🎉