primer/css
1
1
Fork 0
mirror of https://github.com/primer/css.git synced 2024-11-13 08:04:16 +03:00
Code Issues Projects Releases Wiki Activity

update release branch docs + remove storybook publishing docs

Browse Source
This commit is contained in:
Emily 2018-07-03 10:45:22 -07:00
parent 80135b92a2
commit 1916f6b81b
1 changed files with 12 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
RELEASING.md
View File

@ -3,20 +3,21 @@
### In `primer/primer`:
1. Create a new release branch from `dev` and name it `release-<version>`.
1. Go through the tracking PR and make sure everything that should be merged in is merged in.
2. 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.
3. Run the version bump in your terminal: `npm run bump`.
4. Test your changes with the latest release candidate version in the appropriate places (styleguide, storybook, github/github).
5. Once the release PR is approved and you've done necessary testing, merge to `master`. This will trigger a publish to npm.
6. 1. Create a new release branch for the next release from `master` and name it `release-<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)
2. Go through the tracking issue and make sure everything that should be merged in is merged in.
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.
4. Run the version bump in your terminal: `npm run bump`.
5. Test your changes with the latest release candidate version in the appropriate places (styleguide, storybook, github/github).
6. 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`:
@ -53,11 +54,6 @@
1. Edit [index.html](https://github.com/primer/primer.github.io/blob/master/index.html) to include the latest version.
#### Update Storybook
1. Pull the latest from master on primer/primer (after merging in release branch).
2. Run `npm run publish-storybook`.
#### Publish release tag