Bump taskcluster from 44.2.2 to 44.16.1

[dependabot[bot]]

Bumps taskcluster from 44.2.2 to 44.16.1.

Release notes

Sourced from taskcluster's releases.

v44.16.1

GENERAL

▶ [patch] This fixes the default worker state of a worker not known by worker manager to be standalone as opposed to unmanaged to be consistent with the rest of the project. This issue was first brought up in v44.16.0

USERS

▶ [patch] Fix this error (Function listWorkers takes options: continuationToken, limit, quarantined, workerState but was given isQuarantined) while filtering workers based on quaratine status.

v44.16.0

GENERAL

▶ [patch] Don't allow additional properties in worker-response.yml schema. Updated descriptions in worker-response.yml and list-workers-response.yml schemas to explain some default values that may occur in the case where the queue knows about the worker, but worker manager does not. Also, updated the GraphQL queries to extract additional needed data.

▶ [patch] Fix schema validation issues.

▶ [patch] Upgrade node to the latest LTS release, v16.15.1. Also upgrade golangci-lint to 1.46.2.

▶ [patch] Upgrade to go1.18.3 from go1.18.2.

DEPLOYERS

▶ [patch] #5042 Add a configuration option to disable CORS configuration for the queue's S3 client. This is a step forward for supporting minio as a S3 backend.

▶ [patch] #5043 Add a configuration option to enable s3ForcePathStyle for the queue's S3 client

USERS

▶ [minor] #5085 Allow Taskcluster to rerun single task from github interface.

▶ [patch] Replace rust-crypto by hmac-sha256 in the rust client to help with dependency deduplication

▶ [patch] Update a few rust dependencies in the client crate to help reducing duplicates

v44.15.5

GENERAL

▶ [patch]

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v44.16.1

GENERAL

▶ [patch] This fixes the default worker state of a worker not known by worker manager to be standalone as opposed to unmanaged to be consistent with the rest of the project. This issue was first brought up in v44.16.0

USERS

▶ [patch] Fix this error (Function listWorkers takes options: continuationToken, limit, quarantined, workerState but was given isQuarantined) while filtering workers based on quaratine status.

v44.16.0

GENERAL

▶ [patch] Don't allow additional properties in worker-response.yml schema. Updated descriptions in worker-response.yml and list-workers-response.yml schemas to explain some default values that may occur in the case where the queue knows about the worker, but worker manager does not. Also, updated the GraphQL queries to extract additional needed data.

▶ [patch] Fix schema validation issues.

▶ [patch] Upgrade node to the latest LTS release, v16.15.1. Also upgrade golangci-lint to 1.46.2.

▶ [patch] Upgrade to go1.18.3 from go1.18.2.

DEPLOYERS

▶ [patch] #5042 Add a configuration option to disable CORS configuration for the queue's S3 client. This is a step forward for supporting minio as a S3 backend.

▶ [patch] #5043 Add a configuration option to enable s3ForcePathStyle for the queue's S3 client

USERS

▶ [minor] #5085 Allow Taskcluster to rerun single task from github interface.

▶ [patch] Replace rust-crypto by hmac-sha256 in the rust client to help with dependency deduplication

▶ [patch] Update a few rust dependencies in the client crate to help reducing duplicates

v44.15.5

... (truncated)

Commits

• 91f76db v44.16.1
• 4b5abbd Merge pull request #5502 from taskcluster/matt-boris/useStandaloneOverManaged
• a341e92 fix: use standalone over unmanaged
• 3d85ded Merge pull request #5500 from taskcluster/matt-boris/fixQuarantinedFilter
• f6ababf fix(ui): filter by quarantine status param fix
• d26ab82 v44.16.0
• 68785cd Merge pull request #5483 from taskcluster/dependabot/npm_and_yarn/express-ses...
• 9552fbb build(deps): bump express-session from 1.17.2 to 1.17.3
• 0ba4e9f Merge pull request #5499 from taskcluster/matt-boris/betterDefinedWMSchema
• 02317f3 fix(schema): use explicit values when a worker is
• Additional commits viewable in compare view

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[bot]]

Superseded by #293.