Releases: googleapis/gcp-metadata
v0.8.0
This release has breaking changes. Please take care when upgrading to the latest version.
Dropped support for Node.js 4.x and 9.x
This library is no longer tested against versions 4.x and 9.x of Node.js. Please upgrade to the latest supported LTS version!
Return type of instance() and project() has changed
The instance() and project() methods are much more selective about which properties they will accept.
The only accepted properties are params and properties. The instance() and project() methods also now directly return the data instead of a response object.
Changes in how large number valued properties are handled
Previously large number-valued properties were being silently losing precision when
returned by this library (as a number). In the cases where a number valued property
returned by the metadata service is too large to represent as a JavaScript number, we
will now return the value as a BigNumber (from the bignumber.js) library. Numbers that
do fit into the JavaScript number range will continue to be returned as numbers.
For more details see #74.
Breaking Changes
Implementation Changes
- fix: properly handle large numbers in responses (#74)
Dependencies
- chore(deps): update dependency pify to v4 (#73)
Internal / Testing Changes
- Move to the new github org (#84)
- Update CI config (#83)
- Retry npm install in CI (#81)
- Update CI config (#79)
- chore(deps): update dependency nyc to v13 (#77)
- add key for system tests
- increase kitchen test timeout
- add a lint npm script
- update npm scripts
- add a synth file and run it (#75)
- chore(deps): update dependency assert-rejects to v1 (#72)
- chore: ignore package-log.json (#71)
- chore: update renovate config (#70)
- test: throw on deprecation
- chore(deps): update dependency typescript to v3 (#67)
- chore: make it OSPO compliant (#66)
- chore(deps): update dependency gts to ^0.8.0 (#65)
v0.7.0
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
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
v0.6.5
v0.6.4
This is a bug-fix release. Unexpected errors are no longer swallowed by isAvailable. Due to automation bugs, this release didn't end up getting published to npm.
Commits
- 2d34f9d fix: do not swallow unexpected errors (#57)
- 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