Skip to content

build(deps): Bump taskcluster from 30.0.2 to 30.1.0 in /tools #539

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

Merged
merged 1 commit into from
Jun 8, 2020

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps taskcluster from 30.0.2 to 30.1.0.

Release notes

Sourced from taskcluster's releases.

v30.1.0

DEPLOYERS

▶ [minor] #2877 The wmworkers_entities table has now been migrated to use a relational table. The new table is called workers. wmworkers_entities will get deleted.

v30.0.5

DEVELOPERS

▶ [patch] Release tasks now have access to taskcluster-proxy

v30.0.4

NOTE Release automation for this release failed, so there are no docker images, binaries, or released client libraries.

OTHER

▶ Additional change not described here: #2921.

v30.0.3

NOTE Release automation for this release failed, so there are no docker images, binaries, or released client libraries.

GENERAL

▶ [patch] bug 1631824 The worker-manager azure provider now properly tracks and deletes all disks when a virtual machine has data disks created for it.

DEPLOYERS

▶ [patch] A bug in the Azure provider which caused provisioning to fail when handling operations has been fixed.

▶ [patch] Taskcluster services now include metadata at the top level of Fields for generic.* logging messages, rather than in meta or fields sub-properties.

WORKER-DEPLOYERS

▶ [patch] #2969 Docker-worker now only considers itself idle if its call to queue.claimWork returns no tasks. This prevents the situation where a very short afterIdleSeconds causes the worker to shut down while calling claimWork.

▶ [patch] #2925 Listing workers in the "stopping" state will no longer cause 500 errors.

USERS

▶ [patch] bug 1632929 Taskcluster-Github now uses a release event's target_commitish property instead of the tag property to determine the SHA of the released commit. This is important in cases where tags are created as part of the release-creation call, as GitHub sends the release event before the tag is created.

DEVELOPERS

... (truncated)
Changelog

Sourced from taskcluster's changelog.

v30.1.0

DEPLOYERS

▶ [minor] #2877 The wmworkers_entities table has now been migrated to use a relational table. The new table is called workers. wmworkers_entities will get deleted.

v30.0.5

DEVELOPERS

▶ [patch] Release tasks now have access to taskcluster-proxy

v30.0.4

OTHER

▶ Additional change not described here: #2921.

v30.0.3

GENERAL

▶ [patch] bug 1631824 The worker-manager azure provider now properly tracks and deletes all disks when a virtual machine has data disks created for it.

DEPLOYERS

▶ [patch] A bug in the Azure provider which caused provisioning to fail when handling operations has been fixed.

▶ [patch] Taskcluster services now include metadata at the top level of Fields for generic.* logging messages, rather than in meta or fields sub-properties.

WORKER-DEPLOYERS

▶ [patch] #2969 Docker-worker now only considers itself idle if its call to queue.claimWork returns no tasks. This prevents the situation where a very short afterIdleSeconds causes the worker to shut down while calling claimWork.

▶ [patch] #2925 Listing workers in the "stopping" state will no longer cause 500 errors.

USERS

▶ [patch] bug 1632929 Taskcluster-Github now uses a release event's target_commitish property instead of the tag property to determine the SHA of the released commit. This is important in cases where tags are created as part of the release-creation call, as GitHub sends the release event before the tag is created.

... (truncated)
Commits

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 use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

@dependabot-preview dependabot-preview bot added the tools Common Python tools label Jun 8, 2020
@marco-c marco-c merged commit 1672464 into master Jun 8, 2020
@marco-c marco-c deleted the dependabot/pip/tools/taskcluster-30.1.0 branch June 8, 2020 09:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tools Common Python tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant