Closed greenkeeper[bot] closed 6 years ago
coveralls
commented
6 years ago Coverage remained the same at 98.75% when pulling 56900dea652eb84eeda42fb832da5cfae729be2b on greenkeeper/semantic-release-15.1.7 into 319993aff3314684b673fe395bbfb57a2ad8507e on master.
coveralls
commented
6 years ago Coverage remained the same at 98.75% when pulling 56900dea652eb84eeda42fb832da5cfae729be2b on greenkeeper/semantic-release-15.1.7 into 319993aff3314684b673fe395bbfb57a2ad8507e on master.
greenkeeper[bot]
commented
6 years ago Update to this version instead š
The new version differs by 4 commits.
b9bd650 fix(package): update env-ci to version 2.0.06e15c18 chore(package): update p-retry to version 2.0.05af9031 docs: add details on NPM error 403 to troubleshooting doc218aa32 docs: add semantic-release-chrome to the list of community pluginsSee the full diff
greenkeeper[bot]
commented
6 years ago Update to this version instead š
The new version differs by 8 commits.
e88ac63 fix: fix Bitbucket authenticated URLa52f258 refactor: rename origin parameters to repositoryUrl3f61453 test: prevent username/password prompt in get-git-auth-url testsd15905c fix: verify the local branch is up to date with the remote onea11da0d docs: fix jsdoc typos65aaa77 refactor: remove unused test util function45d7e6f fix: unshallow repository with credentialsc02b5ca chore(package): update sinon to version 5.0.1See the full diff
āļø Greenkeeperās updated Terms of Service will come into effect on April 6th, 2018.
Version 15.1.7 of semantic-release was just published.
The version 15.1.7 is not covered by your current version range.
If you donāt accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
It might be worth looking into these changes and trying to get this project onto the latest version of semantic-release.
If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you donāt have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.
Release Notes
v15.1.715.1.7 (2018-04-12)
Bug Fixes
.gittorepositoryUrlonly if it's present in the configured URL (cb1f80c)Commits
The new version differs by 68 commits.
cb1f80cfix: add trailing.gittorepositoryUrlonly if it's present in the configured URL7c9ec41fix(package): update git-url-parse to version 9.0.0a1138a6docs: update plugins package name6172eb8docs: add plugins to the community list31ad231fix: match tag totagFormatfrom the begining of the stringa8a07b7docs: clarify FAQ to publish non-JavaScript packages02746aafix(package): update git-url-parse to version 8.3.1e41726cdocs: fix grammar and typos in CI configuration, configuration, and shareable configurations51e340ffix: handle case with no last release in history30ee231fix: prevent git prompt before permissions verification3c46455fix: removeexecatimeoutdff0a34docs: add "Introduction to Semantic Release" article7c48afafix: prevent git CLI to prompt user/password on CIc84ac15fix(package): Remove commander.js dependency (#704)5f1d530feat: allow to use shorthand forrepositoryUrlThere are 68 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those donāt help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: