1
1
mirror of https://github.com/primer/css.git synced 2024-11-24 13:15:00 +03:00

Merge branch 'release-10.7.0' into delete_dev

This commit is contained in:
Jon Rohan 2018-06-25 20:36:44 -07:00
commit ce52c26633
6 changed files with 26115 additions and 5 deletions

View File

@ -135,9 +135,9 @@ This section is targeted at maintainers of primer, to instruct them on the proce
1. Create a new branch
2. Update the primer version in your terminal `npm install primer@<version>`.
2. Update the primer version in your terminal `bin/npm install primer@<version>`.
3. Update `stylelint-config-primer` in your terminal to the appropriate version `npm install stylelint-config-primer@latest`.
3. Update `stylelint-config-primer` in your terminal to the appropriate version `bin/npm install stylelint-config-primer@latest`.
4. 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.

68
RELEASING.md Normal file
View File

@ -0,0 +1,68 @@
## Releasing a new Primer version 🎉
### In `primer/primer`:
1. Create a new release branch from `dev` 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`:
1. Create a new branch
2. Update the primer version in your terminal `bin/npm install primer@<version>`.
3. Update `stylelint-config-primer` in your terminal to the appropriate version `bin/npm install stylelint-config-primer@latest`.
4. 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.
5. Add reviewers.
6. Check that every deleted vendor file has an accompanying updated vendor file and that the version numbers look correct.
7. Test on review-lab.
8. When ready, merge! 🎉
## Other items that need to be done after publishing Primer
#### Update the Style Guide
1. In [github/styleguide](https://github.com/github/styleguide), update `primer` to your newly released version in your terminal:
`npm install primer@latest`
2. Then run: `script/update-primer-docs`.
3. Commit changes, make PR, get it approved, merge! 🚀
#### Update [primer.github.io](primer.github.io)
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
1. Create a new release tag [here](https://github.com/primer/primer/releases/new).
2. Copy the changes from the [CHANGELOG](https://github.com/primer/primer/blob/master/CHANGELOG.md) and paste it into the release notes.
3. Publish 🎉

View File

@ -32,7 +32,7 @@
"primer-support": "4.5.4"
},
"peerDependencies": {
"primer-buttons": ">=2.5.0"
"primer-buttons": "2.5.5"
},
"keywords": [
"css",

View File

@ -27,7 +27,7 @@
"primer-support": "4.5.4"
},
"peerDependencies": {
"primer-box": ">=2.5.0"
"primer-box": "2.5.7"
},
"keywords": [
"github",

View File

@ -1,5 +1,5 @@
{
"version": "10.6.1",
"version": "10.7.0",
"name": "primer",
"description": "Primer is the CSS framework that powers GitHub's front-end design. primer includes 23 packages that are grouped into 3 core meta-packages for easy install. Each package and meta-package is independently versioned and distributed via npm, so it's easy to include all or part of Primer within your own project.",
"homepage": "http://primer.github.io/",

26042
package-lock.json generated Normal file

File diff suppressed because it is too large Load Diff