Skip to content

chore: release

chore: release #263

Triggered via pull request November 4, 2024 14:50
@vanthomevanthome
synchronize #119
next
Status Success
Total duration 1m 37s
Artifacts

build-test-gql-bot.yaml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

2 errors and 2 warnings
Unhandled error: packages/gql-bot/src/client.ts#L216
Error: {"code":403,"message":"Access denied"} ❯ Client.post src/client.ts:216:13 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 ❯ YamlStreamReadTransformer.<anonymous> src/job_processor_gql.ts:87:32 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { isOperational: true } This error originated in "test/job_processor.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "a job should error when encountering IoRestorecommerceStatusOperationStatus". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
Unhandled error: packages/gql-bot/src/client.ts#L216
Error: {"code":403,"message":"Access denied"} ❯ Client.post src/client.ts:216:13 ❯ processTicksAndRejections node:internal/process/task_queues:95:5 ❯ YamlStreamReadTransformer.<anonymous> src/job_processor_gql.ts:87:32 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { isOperational: true } This error originated in "test/job_processor.spec.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "a job should error when encountering IoRestorecommerceStatusStatus". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.
build / build
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
test / test
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/