@arcane-utils/tasks

Running the tests

The tests create real tasks on Cloud Tasks, so they need credentials/adscale_staging_service_account.json to be reachable from this folder. Use a symlink to keep one version of the credentials: ln -s ../../credentials arcane-utils/tasks/credentials.

They target the default queue on purpose. Each run enqueues three tasks pointing at a fake host, which then fail delivery and retry, so keep them off a queue that real work flows through.

CHANGE LOG

V 1.4.2

Fix gRPC channel leak: createTask now caches one CloudTasksClient

V 1.4.1

Point @arcane-utils/error at ^1.1.20 Use caret ranges for @arcane-utils dependencies, so a published patch or minor is picked up without a manual sweep of every package

V 1.4.0

Security: bump @google-cloud/tasks from 3.2.0 to 7.1.0. The 0.2.0 - 3.2.0 range pulls protobufjs 7.2.4 (critical prototype pollution and arbitrary code execution) plus @grpc/grpc-js and google-gax advisories Requires node 22, matching the publish workflows

V 1.3.0

Security: resolve the service account email through the Cloud Tasks auth layer instead of reading and parsing the credential file, removing a file inclusion sink Update @google-cloud/tasks to 3.2.0 and build/test tooling (typescript 5.9.3, tsup 8.5.1, ts-jest 29.4.12)

V 1.2.8

Use commonjs module

V 1.2.7

Enable using oauth token when creating a task

V 1.2.1

Improve return of the create task function

V 1.2.0

Add the possibility to delay tasks

V 1.1.12

Finally make package functional after many tries

V 1.0.1

Expose google package lib.

V 1.0.0

Init component.