build(deps): bump taskcluster from 47.1.2 to 50.1.3 in /report

[dependabot]

Bumps taskcluster from 47.1.2 to 50.1.3.

Release notes

Sourced from taskcluster's releases.

v50.1.3

ADMINS

▶ [patch] #5621 Github service patch incorrect query for fetching older builds

v50.1.2

ADMINS

▶ [patch] #5621 Several Github service improvements:

• auto cancel task groups is not enabled by default
• auto cancel task groups reports when it cannot seal and cancel task groups with github comments
• when cancelling task groups, it will filter by same event type (push, pull_request, etc)
• calling queue with limited scopes: assumes repo:github.com/org/repo:* role(s) to make sure that given repository has correct permissions to seal and cancel task groups
• github api exposes github.cancelBuilds({ organization, repository, sha?, pullNumber? }) to cancel existing running builds

v50.1.1

GENERAL

▶ [patch] Aligned platforms of released binaries:

• darwin/amd64
• darwin/arm64
• freebsd/amd64
• freebsd/arm64
• linux/amd64
• linux/arm64
• windows/386
• windows/amd64

Previously there were inconsistencies across tools (e.g. taskcluster cli was released for different platforms than livelog).

ADMINS

▶ [patch] #5621 Extend static/taskcluster/github client with two scopes that are necessary to seal and cancel previously created task groups: queue:cancel-task-group:taskcluster-github and queue:seal-task-group:taskcluster-github. When github repository is using a different schedulerId than taskcluster-github, then it might be necessary to update corresponding repo:github.com/ roles with correct scopes.

USERS

▶ [patch] Adds interactive changelog viewer to the docs section.

v50.1.0

GENERAL

▶ [patch] Bump caniuse-lite version with npx update-browserslist-db@latest due to outdated warning.

... (truncated)

Changelog

Sourced from taskcluster's changelog.

v50.1.3

ADMINS

▶ [patch] #5621 Github service patch incorrect query for fetching older builds

v50.1.2

ADMINS

▶ [patch] #5621 Several Github service improvements:

• auto cancel task groups is not enabled by default
• auto cancel task groups reports when it cannot seal and cancel task groups with github comments
• when cancelling task groups, it will filter by same event type (push, pull_request, etc)
• calling queue with limited scopes: assumes repo:github.com/org/repo:* role(s) to make sure that given repository has correct permissions to seal and cancel task groups
• github api exposes github.cancelBuilds({ organization, repository, sha?, pullNumber? }) to cancel existing running builds

v50.1.1

GENERAL

▶ [patch] Aligned platforms of released binaries:

• darwin/amd64
• darwin/arm64
• freebsd/amd64
• freebsd/arm64
• linux/amd64
• linux/arm64
• windows/386
• windows/amd64

Previously there were inconsistencies across tools (e.g. taskcluster cli was released for different platforms than livelog).

ADMINS

▶ [patch] #5621 Extend static/taskcluster/github client with two scopes that are necessary to seal and cancel previously created task groups: queue:cancel-task-group:taskcluster-github and queue:seal-task-group:taskcluster-github. When github repository is using a different schedulerId than taskcluster-github, then it might be necessary to update corresponding repo:github.com/ roles with correct scopes.

USERS

▶ [patch] Adds interactive changelog viewer to the docs section.

v50.1.0

... (truncated)

Commits

• 18be4fe v50.1.3
• 92b000e Merge pull request #6242 from taskcluster/feature/fix-cancelling
• 4087806 Merge pull request #6240 from taskcluster/matt-boris/removeDockerEngineRef
• c623dd1 feat(github): Fix incorrect query for auto-cancellation of builds
• 25afc6f Merge pull request #6241 from taskcluster/renovate/git.colasdn.top-sirupsen-logrus...
• c031366 Update module github.com/sirupsen/logrus to v1.9.2
• af36e9d chore: remove docker engine reference
• 1406f83 Update client-web test to avoid using env variables in regexp (#6239)
• a5bfa50 v50.1.2
• f1f317f Auto-cancellation improvements (#6233)
• 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]

Superseded by #1932.