The version 2.0.0 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 conventional-github-releaser.
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.
Options supported by github (https://www.npmjs.com/package/github)
can no longer be provided through the auth parameter to conventional-github-releaser.
To set a custom URL for GitHub please do one of the following:
If calling the conventional-github-releaser API, pass a URL as the url property of the auth parameter to conventional-github-releaser. The URL should be the fully qualified
domain and path of the GitHub API, such as https://api.github.com or https://api.github.example.com.
If calling the conventional-github-releaser CLI, either pass a URL
using the --url option, or set the CONVENTIONAL_GITHUB_URL
environment variable.
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).
Coverage remained the same at 95.556% when pulling cd75e9d73097b156dc150e2ed88c4b62350eff82 on greenkeeper/conventional-github-releaser-2.0.0 into a1bb423c9147a08079a4a21cf65fda7add137a2b on master.
Version 2.0.0 of conventional-github-releaser was just published.
The version 2.0.0 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 conventional-github-releaser.
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
v2.0.0Features
BREAKING CHANGES
github
package has been replaced bygh-got
.Options supported by
github
(https://www.npmjs.com/package/github)can no longer be provided through the
auth
parameter toconventional-github-releaser
.To set a custom URL for GitHub please do one of the following:
conventional-github-releaser
API, pass a URL as theurl
property of theauth
parameter toconventional-github-releaser
. The URL should be the fully qualifieddomain and path of the GitHub API, such as
https://api.github.com
orhttps://api.github.example.com
.conventional-github-releaser
CLI, either pass a URLusing the
--url
option, or set theCONVENTIONAL_GITHUB_URL
environment variable.
GITHUB_ENDPOINT
environmentvariable supported by the underlying
gh-got
library - https://www.npmjs.com/package/gh-got#endpointCommits
The new version differs by 3 commits.
7f5b57b
docs(README): add Code Coverage badge
45ce4d9
Merge pull request #49 from destroyerofbuilds/feat/github-enterprise
de6d812
feat: support GitHub Enterprise in CLI
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: