Go to file

Stephan Bönnemann a540c402a9 fix(version): use $npm_config_registry variable to ensure the right registry

BREAKING CHANGE: This breaks the usage of the `semantic-release` CLI outside of npm scripts.

2015-02-04 18:56:31 +01:00

bin

test: setup private npm registry w/sinopia

2015-02-04 15:23:16 +01:00

lib

fix(version): use $npm_config_registry variable to ensure the right registry

2015-02-04 18:56:31 +01:00

src

refator: use error-first-handler

2015-02-03 20:45:03 +01:00

tests

test(prepublish): initial scenario

2015-02-04 15:39:05 +01:00

.gitignore

test: setup private npm registry w/sinopia

2015-02-04 15:23:16 +01:00

.travis.yml

test(create-module): helper to create fresh repo/module

2015-02-04 15:23:21 +01:00

package.json

test(install): initial scenario

2015-02-04 15:23:30 +01:00

README.md

docs(readme): fix json syntax

2015-02-02 16:33:57 +01:00

README.md

semantic-release

npm i semantic-release

semantic-release provides "prepublish" and "postpublish" hooks so you automatically release the correct version.

Run semantic-release pre right before npm publish and semantic-release post right after.

For maximum comfort you can automate this inside your package.json:

"scripts": {
  "prepublish": "semantic-release pre",
  "postpublish": "semantic-release post"
}

Note: Even though semantic-release works around a limitation in npm's "prepublish" hook using it prints an error that you can safely ignore. See npm/npm#7118.

MIT License 2015 Stephan Bönnemann