Update google-auth-library to the latest version 🚀

Version 2.0.0 of google-auth-library was just published.

Dependency	google-auth-library
Current Version	1.6.1
Type	dependency

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 google-auth-library.

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.0

Well hello 2.0 🎉 This release has multiple breaking changes. It also has a lot of bug fixes.

Breaking Changes

Support for node.js 4.x and 9.x has been dropped

These versions of node.js are no longer supported.

The `getRequestMetadata` method has been deprecated

The getRequestMetadata method has been deprecated on the IAM, OAuth2, JWT, and JWTAccess classes. The getRequestHeaders method should be used instead. The methods have a subtle difference: the getRequestMetadata method returns an object with a headers property, which contains the authorization header. The getRequestHeaders method simply returns the headers.

Old code

const client = await auth.getClient();
const res = await client.getRequestMetadata();
const headers = res.headers;

New code

const client = await auth.getClient();
const headers = await client.getRequestHeaders();

The `createScopedRequired` method has been deprecated

The createScopedRequired method has been deprecated on multiple classes. The createScopedRequired and createScoped methods on the JWT class were largely in place to help inform clients when scopes were required in an application default credential scenario. Instead of checking if scopes are required after creating the client, instead scopes should just be passed either into the GoogleAuth.getClient method, or directly into the JWT constructor.

Old code

auth.getApplicationDefault(function(err, authClient) {
   if (err) {
     return callback(err);
   }
  if (authClient.createScopedRequired && authClient.createScopedRequired()) {
    authClient = authClient.createScoped([
      'https://www.googleapis.com/auth/cloud-platform'
    ]);
  }
  callback(null, authClient);
});

New code

const client = await auth.getClient({
  scopes: ['https://www.googleapis.com/auth/cloud-platform']
});

The `refreshAccessToken` method has been deprecated

The OAuth2.refreshAccessToken method has been deprecated. The getAccessToken, getRequestMetadata, and request methods will all refresh the token if needed automatically. There is no need to ever manually refresh the token.

As always, if you run into any problems... please let us know!

Features

Set private_key_id in JWT access token header like other google auth libraries. (#450)

Bug Fixes

fix: support HTTPS proxies (#405)
fix: export missing interfaces (#437)
fix: Use new auth URIs (#434)
docs: Fix broken link (#423)
fix: surface file read streams (#413)
fix: prevent unhandled rejections by avoid .catch (#404)
fix: use gcp-metadata for compute credentials (#409)
Add Code of Conduct
fix: Warn when using user credentials from the Cloud SDK (#399)
fix: use Buffer.from instead of new Buffer (#400)
fix: Fix link format in README.md (#385)

Breaking changes

chore: deprecate getRequestMetadata (#414)
fix: deprecate the createScopedRequired methods (#410)
fix: drop support for node.js 4.x and 9.x (#417)
fix: deprecate the refreshAccessToken methods (#411)
fix: deprecate the getDefaultProjectId method (#402)
fix: drop support for node.js 4 (#401)

Build / Test changes

Run synth to make build tools consistent (#455)
Add a package.json for samples and cleanup README (#454)
chore(deps): update dependency typedoc to ^0.12.0 (#453)
chore: move examples => samples + synth (#448)
chore(deps): update dependency nyc to v13 (#452)
chore(deps): update dependency pify to v4 (#447)
chore(deps): update dependency assert-rejects to v1 (#446)
chore: ignore package-lock.json (#445)
chore: update renovate config (#442)
chore(deps): lock file maintenance (#443)
chore: remove greenkeeper badge (#440)
test: throw on deprecation
chore: add intelli-espower-loader for running tests (#430)
chore(deps): update dependency typescript to v3 (#432)
chore(deps): lock file maintenance (#431)
test: use strictEqual in tests (#425)
chore(deps): lock file maintenance (#428)
chore: Configure Renovate (#424)
chore: Update gts to the latest version 🚀 (#422)
chore: update gcp-metadata for isAvailable fix (#420)
refactor: use assert.reject in the tests (#415)
refactor: cleanup types for certificates (#412)
test: run tests with hard-rejection (#397)
cleanup: straighten nested try-catch (#394)
test: getDefaultProjectId should prefer config (#388)
chore(package): Update gts to the latest version 🚀 (#387)
chore(package): update sinon to version 6.0.0 (#386)

Commits

The new version differs by 50 commits.

17a9d5f fix CircleCI install config
dbe05e8 Fix sample and system tests
55885a3 Fix sample and system tests
b9a809c Fix sample and system tests
6e3bc6e Release v2.0.0 (#456)
5377684 fix: support HTTPS proxies (#405)
3ba8c45 Run synth to make build tools consistent (#455)
909fa75 Add a package.json for samples and cleanup README (#454)
dc1265f chore(deps): update dependency typedoc to ^0.12.0 (#453)
0ad3630 chore: move examples => samples + synth (#448)
edcafbc Set private_key_id in JWT access token header like other google auth libraries. (#450)
7e21777 chore(deps): update dependency nyc to v13 (#452)
bad4321 chore(deps): update dependency pify to v4 (#447)
552a4a2 chore(deps): update dependency assert-rejects to v1 (#446)
9cdfb6f chore: ignore package-lock.json (#445)

There are 50 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:

sohwendy / secretary-bot