Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update dependency gcp-metadata to ^0.7.0 #807

Merged
merged 1 commit into from
Jul 17, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 17, 2018

This Pull Request updates dependency gcp-metadata from ^0.6.3 to ^0.7.0

Release Notes

v0.7.0

Compare Source
This is a re-release of v0.6.5 (which was unpublished) as a semver major
(v0.7.0). The potentially breaking change is how we deal with unexpected errors
in the isAvailable function. Previously unexpected errors would be swallowed,
but now they get thrown.

Notable Changes
  • 2d34f9d fix: do not swallow unexpected errors (#​57)
Other commits

Since 0.6.3:

  • 5e74a0e refactor: use mocha instead of ava (#​63)
  • 475081e build: fix typo in publish step (#​59)
  • 89ebf0f chore(deps): update dependency nyc to v12 (#​53)
  • 3cb8173 chore(deps): update dependency gts to ^0.7.0 (#​55)
  • f18fab2 docs: document isAvailable method (#​52)
  • 1da2e85 chore: update to the latest version of all dependencies (#​51)
  • 4305f3f docs: add a few things to the readme (#​50)
  • e1d448d chore(build): test node10, separate lint job (#​49)
  • 360474f Update renovate.json


This PR has been generated by Renovate Bot.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Jul 17, 2018
@JustinBeckwith JustinBeckwith merged commit 94b8e3b into master Jul 17, 2018
@renovate renovate bot deleted the renovate/gcp-metadata-0.x branch July 17, 2018 02:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes This human has signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants