Action failed: The process '/opt/hostedtoolcache/sonar-scanner-cli/7.2.0.5079/linux-x64/bin/sonar-scanner' failed with exit code 3

Process completed with exit code 1.

@tokens-studio/figma-plugin#test: command (/home/runner/work/figma-plugin/figma-plugin/packages/tokens-studio-for-figma) yarn run test exited (1)

Error: Command failed: cd packages/tokens-studio-for-figma && npm run test:coverage:ci && cd ../.. && mv packages/tokens-studio-for-figma/coverage-summary.json coverage-summary.json npm warn config ignoring workspace config at /home/runner/work/figma-plugin/figma-plugin/packages/tokens-studio-for-figma/.npmrc npm warn config ignoring workspace config at /home/runner/work/figma-plugin/figma-plugin/packages/tokens-studio-for-figma/.npmrc npm warn config ignoring workspace config at /home/runner/work/figma-plugin/figma-plugin/packages/tokens-studio-for-figma/.npmrc ● Tokens Studio sync › Updates token set order expect(jest.fn()).toHaveBeenCalled() Expected number of calls: >= 1 Received number of calls: 0 513 | await delay(500); 514 | > 515 | expect(mockMutate).toHaveBeenCalled(); | ^ 516 | expect(mockMutate).toHaveBeenCalledWith({ 517 | mutation: UPDATE_TOKEN_SET_ORDER_MUTATION, 518 | variables: { at Object.<anonymous> (src/app/store/models/reducers/__tests__/tokensStudio.test.ts:515:24) ● Tokens Studio REST API Integration › Token Sets › creates a token set Auth failed: OAuth password grant is disabled on the staging server. Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable. Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ... 21 | beforeAll(async () => { 22 | if (!authToken) { > 23 | throw new Error( | ^ 24 | 'Auth failed: OAuth password grant is disabled on the staging server.\n' + 25 | 'Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable.\n' + 26 | 'Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ...' at Object.<anonymous> (src/utils/tokensStudio/__tests__/restApi.int.test.ts:23:13) ● Tokens Studio REST API Integration › Token Sets › updates a token set Auth failed: OAuth password grant is disabled on the staging server. Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable. Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ... 21 | beforeAll(async () => { 22 | if (!authToken) { > 23 | throw new Error( | ^ 24 | 'Auth failed: OAuth password grant is disabled on the staging server.\n' + 25 | 'Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable.\n' + 26 | 'Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ...' at Object.<anonymous> (src/utils/tokensStudio/__tests__/restApi.int.test.ts:23:13) ● Tokens Studio REST API Integration › Token Sets › deletes a token set Auth failed: OAuth password grant is disabled on the staging server. Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable. Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ... 21 | beforeAll(async () => { 22 | if (!authToken) { > 23 | throw new Error( | ^ 24 | 'Auth failed: OAuth password grant is disabled on the staging server.\n' + 25 | 'Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable.\n' + 26 | 'Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ...' at Object.<anonymous> (src/utils/tokensStudio/__tests__/restApi.int.test.ts:23:13) ● Tokens Studio REST API Integration › Tokens › creates a token Auth failed: OAuth password grant is disabled on the staging server. Please supply a valid token via TOKENS_STUDIO_AUTH_TOKEN environment variable. Example: TOKENS_STUDIO_AUTH_TOKEN=your_token yarn test ... 21 | beforeAll(async () => { 22 | if (!authToken) { > 23 | throw new Error( | ^ 24 | 'Auth failed: OAuth password grant is disabled on the staging server.\n' + 25 | 'Please supply a valid token via TOKEN

Cypress tests: 1 failed

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, SonarSource/sonarqube-scan-action@v6. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, actions/upload-artifact@v4, peter-evans/create-or-update-comment@v4, peter-evans/find-comment@v3. 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.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-node@v3, anuraag016/Jest-Coverage-Diff@master. 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/