|
3 | 3 |
|
4 | 4 | ### In `primer/primer`: |
5 | 5 |
|
6 | | -1. Create a new release branch from `dev` and name it `release-<version>`. |
7 | 6 |
|
8 | | - (CI will publish a release candidate version to npm for branches prefixed with `release`. These version numbers have a `rc.<number>` suffix on them) |
| 7 | +1. Go through the tracking PR and make sure everything that should be merged in is merged in. |
| 8 | + |
| 9 | +2. To update the change log for your release, click on the details links for the continuous-integration/travis-ci/push build. Expand the `Deploying application` output and copy the change log content. Update the [CHANGELOG.md](https://github.com/primer/primer/blob/master/CHANGELOG.md) file with the change log content from the build. |
9 | 10 |
|
10 | | -2. Go through the tracking issue and make sure everything that should be merged in is merged in. |
| 11 | +3. Run the version bump in your terminal: `npm run bump`. |
11 | 12 |
|
12 | | -3. 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](https://github.com/primer/primer/blob/master/CHANGELOG.md) file. |
| 13 | +4. Test your changes with the latest release candidate version in the appropriate places (styleguide, storybook, github/github). |
13 | 14 |
|
14 | | -4. Run the version bump in your terminal: `npm run bump`. |
| 15 | +5. Once the release PR is approved and you've done necessary testing, merge to `master`. This will trigger a publish to npm. |
15 | 16 |
|
16 | | -5. Test your changes with the latest release candidate version in the appropriate places (styleguide, storybook, github/github). |
| 17 | +6. Create a new release branch for the next release from `master` and name it `release-<version>`. |
17 | 18 |
|
18 | | -6. Once the release PR is approved and you've done necessary testing, merge to `master`. This will trigger a publish to npm. |
| 19 | + (CI will publish a release candidate version to npm for branches prefixed with `release`. These version numbers have a `rc.<number>` suffix on them) |
19 | 20 |
|
20 | 21 |
|
21 | 22 | ### In `github/github`: |
|
53 | 54 |
|
54 | 55 | 1. Edit [index.html](https://github.com/primer/primer.github.io/blob/master/index.html) to include the latest version. |
55 | 56 |
|
56 | | -#### Update Storybook |
57 | | - |
58 | | -1. Pull the latest from master on primer/primer (after merging in release branch). |
59 | | - |
60 | | -2. Run `npm run publish-storybook`. |
61 | 57 |
|
62 | 58 | #### Publish release tag |
63 | 59 |
|
|
0 commit comments