Release 4.0.0 · hexojs/hexo-cli

Breaking change

More detailed information for hexo not found @stevenjoezhang [#206]
- When hexo binary could not be located, we usually recommend removing the node_modules folder and reinstall the packages.
- $ rm -rf node_modules && npm install --force
fix(init): fix hexo init error with a number target project name @brelian [#200]
- It's now possible to hexo init 888
fix(init): shallow clone and reduce verbosity @curbengh [#129]
- This should result in faster hexo init due to less file download.
- hexo init operates by git clone hexo-starter. With this change, git now just clone recent commit history (shallow clone), instead of full history.
- hexo init is also more quiet while still show error if encountered.
Improve Node 14 compatibility [#185] [#190]

chore: update hexo-starter @curbengh [#147]
chore: add release-drafter @yoshinorin [#165]
ci: drop Node 8 @curbengh [#185]
ci: add GitHub Actions @curbengh [#223]
chore(deps-dev): bump hexo-renderer-marked from 2.0.0 to 3.0.0 [#216]
chore(deps-dev): bump mocha from 6.2.2 to 8.0.1 [#172] [#203] [#209]
- test(mocha): use yml format @curbengh [#192]
chore(deps-dev): bump eslint from 6.8.0 to 7.0.0 [#197]
chore(deps-dev): bump rewire from 4.0.1 to 5.0.0 [#170]
chore(deps): bump chalk from 2.4.2 to 4.0.0 [#131] [#178]
chore(deps-dev): bump sinon from 7.5.0 to 9.0.2 [#151] [#180]
chore(deps-dev): bump nyc from 14.1.1 to 15.0.0 [#149]
chore(deps-dev): bump eslint-config-hexo from 3.0.0 to 4.1.0 [#139] [#143]