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

chore: bump taskcluster-client from 37.1.0 to 37.2.0 #139

Merged

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 21, 2020

Bumps taskcluster-client from 37.1.0 to 37.2.0.

Release notes

Sourced from taskcluster-client's releases.

v37.2.0

DEPLOYERS

▶ [patch] #3513 Node has been upgraded to 12.18.4 to address CVE-2020-8201.

▶ [patch] #3501 The worker-manager expire-errors job now correctly runs the error expiration process.

WORKER-DEPLOYERS

▶ [minor] #3347 The Azure provider now accepts an ignoreFailedProvisioningStates property in its launch configs which will cause it to ignore ProvisioningState/failed/<code> states on VMs. This is specifically useful for ignoring OSProvisioningTimedOut when the Azure VM agent is not running.

▶ [patch] #3346 The Azure provider now looks only for well-understood failure-related states in the Azure API to determine when a worker has failed. In cases where these measures miss an event, (re)registrationTimeouts will terminate the worker.

▶ [patch] #3058 The worker-manager's Azure provider now more accurately tracks the state of workers, and will not mark a worker RUNNING until it has called registerWorker.

OTHER

▶ Additional changes not described here: #3036, #3502, #3503.

Changelog

Sourced from taskcluster-client's changelog.

v37.2.0

DEPLOYERS

▶ [patch] #3513 Node has been upgraded to 12.18.4 to address CVE-2020-8201.

▶ [patch] #3501 The worker-manager expire-errors job now correctly runs the error expiration process.

WORKER-DEPLOYERS

▶ [minor] #3347 The Azure provider now accepts an ignoreFailedProvisioningStates property in its launch configs which will cause it to ignore ProvisioningState/failed/<code> states on VMs. This is specifically useful for ignoring OSProvisioningTimedOut when the Azure VM agent is not running.

▶ [patch] #3346 The Azure provider now looks only for well-understood failure-related states in the Azure API to determine when a worker has failed. In cases where these measures miss an event, (re)registrationTimeouts will terminate the worker.

▶ [patch] #3058 The worker-manager's Azure provider now more accurately tracks the state of workers, and will not mark a worker RUNNING until it has called registerWorker.

OTHER

▶ Additional changes not described here: #3036, #3502, #3503.

Commits
  • f189f51 v37.2.0
  • 1e0ddef Merge pull request #3513 from renovate-bot/renovate/node-12.x
  • a7f6258 Merge pull request #3522 from renovate-bot/renovate/query-string-6.x-lockfile
  • 7ea8f33 Merge pull request #3523 from renovate-bot/renovate/ramda-0.x
  • 1a1b307 Update dependency ramda to ^0.27.0
  • f995d8f Update dependency query-string to v6.13.2
  • 94d766a Merge pull request #3516 from djmitche/issue3503
  • 286d7ed run mock auth tests without azure creds
  • 32bf296 Merge pull request #3515 from renovate-bot/renovate/qs-6.x-lockfile
  • c1207d3 yarn generate plus changelog
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 21, 2020
@codecov
Copy link

codecov bot commented Sep 21, 2020

Codecov Report

Merging #139 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #139   +/-   ##
=======================================
  Coverage   66.24%   66.24%           
=======================================
  Files           4        4           
  Lines         157      157           
=======================================
  Hits          104      104           
  Misses         53       53           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 188ab84...465d2c9. Read the comment docs.

@freaktechnik freaktechnik merged commit c0dda6c into master Sep 21, 2020
@freaktechnik freaktechnik deleted the dependabot/npm_and_yarn/taskcluster-client-37.2.0 branch September 21, 2020 08:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant