2.5 KiB
Releasing a new Primer version 🎉
In primer/primer
:
- Create a new release branch from
dev
and name itrelease-<version>
.
(CI will publish a release candidate version to npm for branches prefixed with release
. These version numbers have a rc.<number>
suffix on them)
-
Go through the tracking issue and make sure everything that should be merged in is merged in.
-
Once your builds finish, click on the details links for the continuous-integration/travis-ci/push build. Expand the
Deploying application
output and you should be able to find an outputted change log here. Copy this and update the CHANGELOG.md file. -
Run the version bump in your terminal:
npm run bump
. -
Test your changes with the latest release candidate version in the appropriate places (styleguide, storybook, github/github).
-
Once the release PR is approved and you've done necessary testing, merge to
master
. This will trigger a publish to npm.
In github/github
:
-
Create a new branch
-
Update the primer version in your terminal
bin/npm install primer@<version>
. -
Update
stylelint-config-primer
in your terminal to the appropriate versionbin/npm install stylelint-config-primer@latest
. -
If you need to make changes to github/github due to the Primer release, make a separate branch. When ready, merge that branch into your release branch.
-
Add reviewers.
-
Check that every deleted vendor file has an accompanying updated vendor file and that the version numbers look correct.
-
Test on review-lab.
-
When ready, merge! 🎉
Other items that need to be done after publishing Primer
Update the Style Guide
- In github/styleguide, update
primer
to your newly released version in your terminal:
npm install primer@latest
-
Then run:
script/update-primer-docs
. -
Commit changes, make PR, get it approved, merge! 🚀
Update primer.github.io
- Edit index.html to include the latest version.
Update Storybook
-
Pull the latest from master on primer/primer (after merging in release branch).
-
Run
npm run publish-storybook
.