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

Update dependency @google-cloud/debug-agent to v2.6.0 #865

Merged
merged 1 commit into from
Nov 29, 2018

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 10, 2018

This PR contains the following updates:

Package Type Update Change References
@​google-cloud/debug-agent dependencies minor 2.4.0 -> 2.6.0 source
@​google-cloud/debug-agent dependencies minor 2.3.2 -> 2.6.0 source

Release Notes

googleapis/cloud-debug-nodejs

v2.6.0

Compare Source

This release adds side-effect-free evaluation #​335 and fixes an issue where when a breakpoint is hit in a transpiled file, the line number of the breakpoint incorrectly changes #​436.

Commits
  • fix: line numbers don't change in transpiled files (#​436) 2d7a0f7
  • docs: fix image links on npmjs.com (#​435) 71ae615
  • chore: remove stripResults parameter (#​432) e42836f
  • chore: clean up test-e2e.ts (#​431) a627642
  • feat: implement side-effect-free expression evaluation (#​335) 173c9e7
  • chore: remove the GCLOUD_USE_INSPECTOR env var (#​429) 73b171e
  • chore: change the gts version to ^0.5.4 (#​427) 54d3d10
  • chore: add tests to verify evaluated expressions (#​425) d03e0e5
  • chore(package): update @​types/node to version 10.0.3 (#​424) cc40309

v2.5.1

Compare Source

This release addresses issue #​420. In particular, if semver version 5.1.0 was already installed as a dependency prior to installing @google-cloud/debug-agent, the agent would have an out of date version of semver and would fail to start.

Commits

v2.5.0

Compare Source

This release adds support for Node 10 by always using the inspector protocol on Node >= 10. This is needed because the vm.runInDebugContext function, needed to use the legacy debug protocol, is no longer available in Node 10.

Commits

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR is stale, or if you modify the PR title to begin with "rebase!".

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


This PR has been generated by Renovate Bot. View repository job log here.

@googlebot googlebot added the cla: yes This human has signed the Contributor License Agreement. label Nov 10, 2018
@renovate renovate bot force-pushed the renovate/google-cloud-debug-agent-2.x branch 16 times, most recently from 6a8e128 to 2214af6 Compare November 13, 2018 18:51
@renovate renovate bot changed the title fix(deps): update dependency @google-cloud/debug-agent to v2.6.0 Update dependency @google-cloud/debug-agent to v2.6.0 Nov 13, 2018
@renovate renovate bot force-pushed the renovate/google-cloud-debug-agent-2.x branch 12 times, most recently from a06df3f to 024fc46 Compare November 15, 2018 04:15
@renovate renovate bot force-pushed the renovate/google-cloud-debug-agent-2.x branch 17 times, most recently from 35c8dc0 to 12923b4 Compare November 29, 2018 06:31
@renovate renovate bot force-pushed the renovate/google-cloud-debug-agent-2.x branch from 12923b4 to a188f2d Compare November 29, 2018 09:56
@fhinkel fhinkel added the kokoro:run Add this label to force Kokoro to re-run the tests. label Nov 29, 2018
@kokoro-team kokoro-team removed the kokoro:run Add this label to force Kokoro to re-run the tests. label Nov 29, 2018
@fhinkel fhinkel merged commit 4250f5e into master Nov 29, 2018
@fhinkel fhinkel deleted the renovate/google-cloud-debug-agent-2.x branch November 29, 2018 13:22
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.

3 participants