0c67ba517f
- 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`.
58 lines
2.1 KiB
JavaScript
Executable File
58 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('-r, --repositoryUrl <repositoryUrl>', 'Git repository URL')
|
|
.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('.')(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);
|
|
}
|
|
}
|
|
};
|