feat: Make semantic-release language agnostic

- Do not rely on `package.json` anymore
- Use `cosmiconfig` to load the configation. `semantic-release` can be configured:
  - via CLI options (including plugin names but not plugin options)
  - in the `release` property of `package.json` (as before)
  - in a `.releaserc.yml` or `.releaserc.js` or `.releaserc.js` or `release.config.js` file
  - in a `.releaserc` file containing `json`, `yaml` or `javascript` module
- Add the `repositoryUrl` options (used across `semantic-release` and plugins). The value is determined from CLi option, or option configuration, or package.json or the git remote url
- Verifies that `semantic-release` runs from a git repository
- `pkg` and `env` are not passed to plugin anymore
- `semantic-release` can be run both locally and globally. If ran globally with non default plugins, the plugins can be installed both globally or locally.

BREAKING CHANGE: `pkg` and `env` are not passed to plugin anymore.
Plugins relying on a `package.json` must verify the presence of a valid `package.json` and load it.
Plugins can use `process.env` instead of `env`.

This commit is contained in:

Pierre Vanduynslager

2017-11-24 21:56:15 -05:00

parent 5bec59b26b

commit 0c67ba517f

11 changed files with 292 additions and 110 deletions

									
										test/integration.test.js
									
		+1
		-1
	
												View File
												
				@@ -7,7 +7,7 @@ import registry from './helpers/registry';

				import mockServer from './helpers/mockserver';

				import semanticRelease from '..';

				/* eslint-disable camelcase */

				/* eslint camelcase: ["error", {properties: "never"}] */

				// Environment variables used with cli

				const env = {