Skip to content

Lock file maintenance (#515) #7529

Lock file maintenance (#515)

Lock file maintenance (#515) #7529

Triggered via push April 6, 2026 10:36
Status Success
Total duration 2m 42s
Artifacts

test.yml

on: push
Matrix: test
All tests passed
3s
All tests passed
Fit to window
Zoom out
Zoom in

Annotations

4 errors and 2 warnings
Unhandled error: packages/job-manager/lib/JobsRepository.js#L52
TypeError: this._JobModel.edit is not a function ❯ JobsRepository.update lib/JobsRepository.js:52:30 ❯ JobManager._jobMessageHandler lib/JobManager.js:130:52 ❯ JobManager.<anonymous> lib/JobManager.js:101:17 This error originated in "test/job-manager.test.js" 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 "can wait for job completion". 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/job-manager/lib/JobManager.js#L405
Error: Job "failed-oneoff" does not exist ❯ Bree.remove ../../node_modules/bree/src/index.js:737:13 ❯ JobManager.removeJob lib/JobManager.js:405:9 This error originated in "test/job-manager.test.js" 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 "sets a finished state on a job". 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/job-manager/lib/JobsRepository.js#L52
TypeError: this._JobModel.edit is not a function ❯ JobsRepository.update lib/JobsRepository.js:52:30 ❯ JobManager._jobMessageHandler lib/JobManager.js:130:52 ❯ JobManager.<anonymous> lib/JobManager.js:101:17 This error originated in "test/job-manager.test.js" 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 "can wait for job completion". 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/job-manager/lib/JobManager.js#L405
Error: Job "failed-oneoff" does not exist ❯ Bree.remove ../../node_modules/bree/src/index.js:737:13 ❯ JobManager.removeJob lib/JobManager.js:405:9 This error originated in "test/job-manager.test.js" 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 "sets a finished state on a job". 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.
Node 22
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Node 24
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/