Skip to content

Commit

Permalink
Add auto-release
Browse files Browse the repository at this point in the history
  • Loading branch information
damassi committed Jan 4, 2019
1 parent 4806ce1 commit 510ff71
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 31 deletions.
12 changes: 12 additions & 0 deletions .autorc
@@ -0,0 +1,12 @@
{
"no-version-prefix": true,
"onlyPublishWithReleaseLabel": true,
"name": "Artsy",
"email": "it@artsymail.com",
"labels": {
"major": "Version: Major",
"minor": "Version: Minor",
"patch": "Version: Patch",
},
"noReleaseLabels": ["Version: Trivial", "Skip Release"]
}
37 changes: 6 additions & 31 deletions README.md
Expand Up @@ -387,39 +387,14 @@ if you have suggestions.
<details>
Circle CI is set up to publish releases to NPM automatically via
[semantic-release][semantic-release] following every successful merge to master.
`react-responsive-media` uses [auto-release](https://github.com/intuit/auto-release#readme) to automatically release on every PR. Every PR should have a label that matches one of the following
Release versions (major, minor, patch) are triggered
[by commit messages][release-commit-message-format], when they adhere to
[Ember conventions][ember-release-format]:
- Version: Trivial
- Version: Patch
- Version: Minor
- Version: Major
```
[TAG context] commit message
```
[Valid tags][release-tags] for release include PATCH, DOC, FIX (patch), FEATURE
(minor), and BREAKING (major). A context is also required. Commits that do not
adhere to this convention will not trigger an NPM release.
##### Example Patch Release
```
[FIX typeface] Add missing unit
[PATCH tooling] Bump version
```
##### Example Minor (Feature) Release
```
[FEATURE ios] Add View primitive
```
##### Example Major (Breaking) Release
```
[BREAKING refactor] Update API to support new platform
```
No release will happen on a `Trivial` update.
</details>
Expand Down

0 comments on commit 510ff71

Please sign in to comment.