e2a8a5cd32
- Run with one command and do not rely on error exit codes to stop the process when a release is not necessary - Break `index.js` in smaller modules in order to improve testability and simplify the code - Add several missing unit and integration tests to reach 100% coverage - Integration tests now test end to end, including publishing to Github (with http://www.mock-server.com on Docker) - Use `tj/commander.js` to print an help message, verify and parse CLI arguments - Semantic-release can now be called via Javascript API: `require('semantic-release')(options)` - Remove npmlog dependency and add more log messages - Logger is now passed to plugins - Add debug logs with `visionmedia/debug`. `debug` is enabled for both semantic-release and plugins with `--debug` - Use `kevva/npm-conf` in place of the deprecated `npm/npmconf` - Pass lastRelease, nextRelease and commits to generate-notes plugin - In dry-run mode, print the release note instead of publishing it to Github as draft, and skip the CI verifications - The dry-run mode does not require npm and Github TOKEN to be set anymore and can be run locally BREAKING CHANGE: Semantic-Release must now be executed with `semantic-release` instead of `semantic-release pre && npm publish && semantic-release post`. BREAKING CHANGE: The `semantic-release` command now returns with exit code 0 on expected exception (no release has to be done, running on a PR, gitHead not found, other CI job failed etc...). It only returns with 1 when there is an unexpected error (code error in a plugin, plugin not found, git command cannot be run etc..). BREAKING CHANGE: Calling the `semantic-release` command with unexpected argument(s) now exit with 1 and print an help message. BREAKING CHANGE: Semantic-Release does not rely on `npmlog` anymore and the log level cannot be configured. Debug logs can be activated with CLI option `--debug` or with environment variable `DEBUG=semantic-release:*` BREAKING CHANGE: The CLI options `--debug` doesn't enable the dry-run mode anymore but activate the debugs. The dry run mode is now set with the CLI command `--dry-run` or `-d`.
29 lines
792 B
JavaScript
Executable File
29 lines
792 B
JavaScript
Executable File
#!/usr/bin/env node
|
|
|
|
// Bad news: We have to write plain ES5 in this file
|
|
// Good news: It's the only file of the entire project
|
|
|
|
var semver = require('semver');
|
|
|
|
if (semver.lt(process.version, '8.0.0')) {
|
|
console.error(
|
|
`semantic-release: node version >= 8 is required. Found ${process.version}.
|
|
|
|
If there is another job running on node version >= 8, it will be picked as
|
|
the build leader and you can safely ignore this message.
|
|
|
|
If you don't have node 8 in your build matrix you can use "npx" to restore
|
|
compatibility with minimal overhead:
|
|
|
|
$ npx -p node@8 npm run semantic-release
|
|
|
|
npx is bundled with npm >= 5.4, or available via npm. More info: npm.im/npx`
|
|
);
|
|
process.exit(1);
|
|
}
|
|
|
|
// node 8+ from this point on
|
|
require('../src/cli')().catch(() => {
|
|
process.exitCode = 1;
|
|
});
|