-
Go through the tracking PR and make sure everything that should be merged in is merged in.
-
To update the change log for your release, click on the details links for the continuous-integration/travis-ci/push build. Expand the
Deploying applicationoutput and copy the change log content. Update the CHANGELOG.md file with the change log content from the build. -
Run the version bump in your terminal:
npm run bump. -
Run
script/check-versionsto double check there are no version conflicts. You may need to update peer dependencies inprimer-popoverandprimer-marketing-buttons. -
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. -
Create a new release branch for the next release from
masterand 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)
-
Create a new branch
-
Update the primer version in your terminal
bin/npm install primer@<version>. -
Update
stylelint-config-primerin 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! 🎉
- In github/styleguide, update
primerto 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.