Skip to content
This repository was archived by the owner on Apr 3, 2024. It is now read-only.

chore: update gcp-metadata to 0.6.3#407

Merged
DominicKramer merged 6 commits intogoogleapis:masterfrom
DominicKramer:chore/update-gcp-metadata-0.6.3
Mar 16, 2018
Merged

chore: update gcp-metadata to 0.6.3#407
DominicKramer merged 6 commits intogoogleapis:masterfrom
DominicKramer:chore/update-gcp-metadata-0.6.3

Conversation

@DominicKramer
Copy link
Copy Markdown
Contributor

@DominicKramer DominicKramer commented Mar 14, 2018

gcp-metadata version 0.6.3 uses Typescript 2.7. Therefore, for this module to compile, its Typescript version has been updated.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Mar 14, 2018
@ofrobots ofrobots changed the title chore: update gcp-metadata to 0.6.3 chore: update gcp-metadata to 0.6.3 Mar 14, 2018
@ofrobots
Copy link
Copy Markdown
Contributor

This commit also changes the typescript version, so the issue title isn't accurate. Is the typescript change intentional?

@DominicKramer
Copy link
Copy Markdown
Contributor Author

The Typescript change is required by the gcp-metadata change. I'll update the description.

This change should fix the unit test, but further investigation is
needed to determine why this change is necessary.
Copy link
Copy Markdown
Contributor

@ofrobots ofrobots left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM w/ nit.

test/nocks.ts Outdated
validator = validator || accept;
return nock('https://accounts.google.com')
.post('/o/oauth2/token', validator)
return nock(/https:\/\/(accounts\.google\.com|www\.googleapis\.com)/)

This comment was marked as spam.

This comment was marked as spam.

@DominicKramer DominicKramer merged commit 9c4c1bb into googleapis:master Mar 16, 2018
DominicKramer added a commit to DominicKramer/cloud-debug-nodejs that referenced this pull request Apr 27, 2018
The current `package.json` requires `semver@'^5.1.0'`.  However,
the `semver.coerce` function does not exist in that version.

As part of PR googleapis#407, `package-lock.json` was regenerated and
specified semver version 5.5.0 should be used.

When the tests were run, Node >= 8 would use package-lock.json
and installed semver 5.5.0 that has `semver.coerce`.

In addition, for Node < 8, the tests would install the latest
version of semver (5.5.0) that has `semver.coerce`.

As a result, the system and unit tests would all pass.

However, if user code, or the code of its dependencies, requires
only semver@'^5.1.0', and that version was installed prior to
installing @google-cloud/debug-agent, version `5.1.0` of semver
could be used.  However since this version doesn't have the
`semver.coerce` function, the debug agent would crash on
startup.  This is what happened in issue googleapis#420.

Fixes: googleapis#420
DominicKramer added a commit that referenced this pull request Apr 27, 2018
The current `package.json` requires `semver@'^5.1.0'`.  However,
the `semver.coerce` function does not exist in that version.

As part of PR #407, `package-lock.json` was regenerated and
specified semver version 5.5.0 should be used.

When the tests were run, Node >= 8 would use package-lock.json
and installed semver 5.5.0 that has `semver.coerce`.

In addition, for Node < 8, the tests would install the latest
version of semver (5.5.0) that has `semver.coerce`.

As a result, the system and unit tests would all pass.

However, if user code, or the code of its dependencies, requires
only semver@'^5.1.0', and that version was installed prior to
installing @google-cloud/debug-agent, version `5.1.0` of semver
could be used.  However since this version doesn't have the
`semver.coerce` function, the debug agent would crash on
startup.  This is what happened in issue #420.

Fixes: #420
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants