d548edcf37
- Add a new plugin type: `publish` - Add support for multi-plugin. A plugin module can now return an object with a property for each plugin type - Uses by default [npm](https://github.com/semantic-release/npm) and [github](https://github.com/semantic-release/github) in addition of Travis for the verify condition plugin - Uses by default [npm](https://github.com/semantic-release/npm) and [github](https://github.com/semantic-release/github) for the publish plugin - `gitTag` if one can be found is passed to `generateNotes` for both `lastRelease` and `nextRelease` - `semantic-release` now verifies the plugin configuration (in the `release` property of `package.json`) and throws an error if it's invalid - `semantic-release` now verifies each plugin output and will throw an error if a plugin returns an unexpected value. BREAKING CHANGE: `githubToken`, `githubUrl` and `githubApiPathPrefix` have to be set at the [github](https://github.com/semantic-release/github) plugin level. They can be set via `GH_TOKEN`, `GH_URL` and `GH_PREFIX` environment variables. BREAKING CHANGE: the `npm` parameter is not passed to any plugin anymore. Each plugin have to read `.npmrc` if they needs to (with https://github.com/kevva/npm-conf for example).
57 lines
2.1 KiB
JavaScript
Executable File
57 lines
2.1 KiB
JavaScript
Executable File
const program = require('commander');
|
|
const logger = require('./lib/logger');
|
|
|
|
function list(values) {
|
|
return values.split(',').map(value => value.trim());
|
|
}
|
|
|
|
module.exports = async () => {
|
|
program
|
|
.name('semantic-release')
|
|
.description('Run automated package publishing')
|
|
.option('-b, --branch <branch>', 'Branch to release from')
|
|
.option(
|
|
'--verify-conditions <paths>',
|
|
'Comma separated list of paths or packages name for the verifyConditions plugin(s)',
|
|
list
|
|
)
|
|
.option('--get-last-release <path>', 'Path or package name for the getLastRelease plugin')
|
|
.option('--analyze-commits <path>', 'Path or package name for the analyzeCommits plugin')
|
|
.option(
|
|
'--verify-release <paths>',
|
|
'Comma separated list of paths or packages name for the verifyRelease plugin(s)',
|
|
list
|
|
)
|
|
.option('--generate-notes <path>', 'Path or package name for the generateNotes plugin')
|
|
.option('--publish <paths>', 'Comma separated list of paths or packages name for the publish plugin(s)', list)
|
|
.option('--debug', 'Output debugging information')
|
|
.option(
|
|
'-d, --dry-run',
|
|
'Dry-run mode, skipping verifyConditions, publishing and release, printing next version and release notes'
|
|
)
|
|
.parse(process.argv);
|
|
|
|
if (program.debug) {
|
|
// Debug must be enabled before other requires in order to work
|
|
require('debug').enable('semantic-release:*');
|
|
}
|
|
|
|
try {
|
|
if (program.args.length > 0) {
|
|
program.outputHelp();
|
|
process.exitCode = 1;
|
|
} else {
|
|
await require('./index')(program.opts());
|
|
}
|
|
} catch (err) {
|
|
// If error is a SemanticReleaseError then it's an expected exception case (no release to be done, running on a PR etc..) and the cli will return with 0
|
|
// Otherwise it's an unexpected error (configuration issue, code issue, plugin issue etc...) and the cli will return 1
|
|
if (err.semanticRelease) {
|
|
logger.log(`%s ${err.message}`, err.code);
|
|
} else {
|
|
process.exitCode = 1;
|
|
logger.error('An error occurred while running semantic-release: %O', err);
|
|
}
|
|
}
|
|
};
|