85dd69b3a2
Add several fixes and improvements in the identification of the last release gitHead: - If there is no last release, unshallow the repo in order to retrieve all existing commits - If git head is not present in last release, try to retrieve it from git tag with format ‘v\<version\>’ or ‘\<version\>’ - If the last release git head cannot be determined and found in commit history, unshallow the repo and try again - Throw a ENOGITHEAD error if the gitHead for the last release cannot be found in the npm metadata nor in the git tags, preventing to make release based on the all the commits in the repo as before - Add integration test for the scenario with a packed repo from which `npm republish` fails to read the git head Fix #447, Fix #393, Fix #280, Fix #276
26 lines
527 B
YAML
26 lines
527 B
YAML
language: node_js
|
|
services:
|
|
- couchdb
|
|
notifications:
|
|
email: false
|
|
node_js:
|
|
- 8
|
|
|
|
# Trigger a push build on caribou and greenkeeper branches + PRs build on every branches
|
|
# Avoid double build on PRs (See https://github.com/travis-ci/travis-ci/issues/1147)
|
|
branches:
|
|
only:
|
|
- caribou
|
|
- /^greenkeeper.*$/
|
|
|
|
# Retry install on fail to avoid failing a build on network/disk/external errors
|
|
install:
|
|
- travis_retry npm install
|
|
|
|
script:
|
|
- npm run test
|
|
|
|
after_success:
|
|
- npm run codecov
|
|
- npm run semantic-release
|