Process completed with exit code 1.

AssertionError: expected [Function] to throw error including 'Failed to load config: Failed to pars…' but got 'Failed to load config: Failed to load…' Expected: "Failed to load config: Failed to parse combined matcher config: Expected ',' or ']' after array element in JSON at position 196" Received: "Failed to load config: Failed to load/parse combined matcher config: Expected ',' or ']' after array element in JSON at position 196 (line 1 column 197), Matcher config is empty" ❯ src/ConfigLoader.test.ts:227:7

AssertionError: expected [Function] to throw error including 'Failed to load config: Failed to pars…' but got 'Failed to load config: Failed to load…' Expected: "Failed to load config: Failed to parse combined matcher config: Expected ',' or ']' after array element in JSON at position 196" Received: "Failed to load config: Failed to load/parse combined matcher config: Expected ',' or ']' after array element in JSON at position 196 (line 1 column 197), Matcher config is empty" ❯ src/ConfigLoader.test.ts:227:7

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: step-security/harden-runner@5ef0c079ce82195b2a36a210272d6b661572d83e. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/