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).
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
githubpackage has been replaced bygh-got.Options supported by
github(https://www.npmjs.com/package/github)can no longer be provided through the
authparameter toconventional-github-releaser.To set a custom URL for GitHub please do one of the following:
conventional-github-releaserAPI, pass a URL as theurlproperty of theauthparameter toconventional-github-releaser. The URL should be the fully qualifieddomain and path of the GitHub API, such as
https://api.github.comorhttps://api.github.example.com.conventional-github-releaserCLI, either pass a URLusing the
--urloption, or set theCONVENTIONAL_GITHUB_URLenvironment variable.
GITHUB_ENDPOINTenvironmentvariable supported by the underlying
gh-gotlibrary - https://www.npmjs.com/package/gh-got#endpointCommits
The new version differs by 3 commits.
7f5b57bdocs(README): add Code Coverage badge45ce4d9Merge pull request #49 from destroyerofbuilds/feat/github-enterprisede6d812feat: support GitHub Enterprise in CLISee 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: