Skip to content

build(deps): bump taskcluster from 14.3.1 to 16.2.0 in /bot#88

Merged
La0 merged 2 commits intomasterfrom
dependabot/pip/bot/taskcluster-16.2.0
Aug 27, 2019
Merged

build(deps): bump taskcluster from 14.3.1 to 16.2.0 in /bot#88
La0 merged 2 commits intomasterfrom
dependabot/pip/bot/taskcluster-16.2.0

Conversation

@dependabot-preview
Copy link
Copy Markdown
Contributor

Bumps taskcluster from 14.3.1 to 16.2.0.

Release notes

Sourced from taskcluster's releases.

v16.2.0

[minor] (bug 1561320) Taskcluster deployments now support sentry error reporting. You can configure this option by setting
an errorConfig at the top-level of your config:

rootUrl: ...
errorConfig:
  reporter: SentryReporter
  dsn: <your sentry dsn>

Errors will be reported to this project and tagged with service/process names in addition to taskcluster
release version.

(bug 1574656) Worker-pool configurations for google-based providers now accept a workerConfig property, which is passed to new workers.
The existing userData property is deprecated.

v16.1.0

[minor] (bug 1572775) * All lib-loader setup functions now get passed their own
name to allow logging more usefully.

  • There is now a document in dev-docs explaining recommended
    monitoring practices.

[minor] (bug 1553953) The workerType identifier now has a more restrictive pattern:

  • consisting of lower-case alphanumeric plus dash (-)
  • from 1 to 38 characters long
  • beginning with a lower-case alphabetic character
  • ending with a lower-case alphanumeric character (not a dash)
    Any worker types not matching this pattern will no longer function as of this version.

This is considered a minor change because no known workerTypes (aside from some
internal testing workerTypes) violate this pattern.

[minor] (bug 1572764) The go client doesn't log the full request in case of an error anymore.
It logs only the method, hostname, port and response body. It logs the
full request when the environment variable TASKCLUSTER_DEBUG is
defined.

[minor] (#1190) Updates a number of config variables including:

  • Setting pulse-namespace per service is no longer supported
  • Services that no longer use aws directly no longer take credentials
  • Setting table names for secrets, notify, and hooks services is no longer supported

The name of the hooks last fires table has changed so you must update your static
client scopes in your deployment from including auth:azure-table:read-write:${azureAccountId}/LastFire
to auth:azure-table:read-write:${azureAccountId}/LastFire3.

v16.0.0

[MAJOR] (bug 1552970) The auth.gcpCredentials method no longer modifies the granting service account.

... (truncated)
Changelog

Sourced from taskcluster's changelog.

v16.2.0

[minor] (bug 1561320) Taskcluster deployments now support sentry error reporting. You can configure this option by setting
an errorConfig at the top-level of your config:

rootUrl: ...
errorConfig:
  reporter: SentryReporter
  dsn: <your sentry dsn>

Errors will be reported to this project and tagged with service/process names in addition to taskcluster
release version.

(bug 1574656) Worker-pool configurations for google-based providers now accept a workerConfig property, which is passed to new workers.
The existing userData property is deprecated.

v16.1.0

[minor] (bug 1572775) * All lib-loader setup functions now get passed their own
name to allow logging more usefully.

  • There is now a document in dev-docs explaining recommended
    monitoring practices.

[minor] (bug 1553953) The workerType identifier now has a more restrictive pattern:

  • consisting of lower-case alphanumeric plus dash (-)
  • from 1 to 38 characters long
  • beginning with a lower-case alphabetic character
  • ending with a lower-case alphanumeric character (not a dash)
    Any worker types not matching this pattern will no longer function as of this version.

This is considered a minor change because no known workerTypes (aside from some
internal testing workerTypes) violate this pattern.

[minor] (bug 1572764) The go client doesn't log the full request in case of an error anymore.
It logs only the method, hostname, port and response body. It logs the
full request when the environment variable TASKCLUSTER_DEBUG is
defined.

[minor] (#1190) Updates a number of config variables including:

  • Setting pulse-namespace per service is no longer supported
  • Services that no longer use aws directly no longer take credentials
  • Setting table names for secrets, notify, and hooks services is no longer supported

The name of the hooks last fires table has changed so you must update your static
client scopes in your deployment from including auth:azure-table:read-write:${azureAccountId}/LastFire
to auth:azure-table:read-write:${azureAccountId}/LastFire3.

... (truncated)
Commits
  • bb08a08 v16.2.0
  • 39c444f Merge pull request #1208 from sciurus/fix-index-namespace
  • 90daa11 Merge pull request #1205 from taskcluster/bug-1561320
  • a1d5050 Fix pulse namespace for index
  • 3572b0d Add docs to dev-docs about error config
  • b901e33 Add a changelog for sentry
  • 1d553d4 Merge pull request #1206 from djmitche/bug1574656
  • 886503e Fix plugin checking
  • ec9a8e7 Add docs on sentry to monitor readme
  • 87543bc Add some nice-to-haves for operators
  • 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 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)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

@La0 La0 merged commit 4f95408 into master Aug 27, 2019
@dependabot-preview dependabot-preview Bot deleted the dependabot/pip/bot/taskcluster-16.2.0 branch August 27, 2019 07:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bot Code review bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant