Canceling since a higher priority waiting request for ci-feat/2062-feature-add-new-compliance-tab-in-sidebar exists

The operation was canceled.

Canceling since a higher priority waiting request for ci-feat/2062-feature-add-new-compliance-tab-in-sidebar exists

The operation was canceled.

Process completed with exit code 1.

Delete `⏎`

Replace `⏎······?·this.complianceIssues().filter((i)·=>·i.category·===·category)⏎·····` with `·?·this.complianceIssues().filter(i·=>·i.category·===·category)`

Replace `⏎······(i)·=>·i.language·===·lang·&&·i.text?.toLowerCase()·===·event.text.toLowerCase(),⏎····` with `i·=>·i.language·===·lang·&&·i.text?.toLowerCase()·===·event.text.toLowerCase()`

Process completed with exit code 1.

Canceling since a higher priority waiting request for ci-feat/2062-feature-add-new-compliance-tab-in-sidebar exists

The operation was canceled.

Canceling since a higher priority waiting request for ci-feat/2062-feature-add-new-compliance-tab-in-sidebar exists

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: Slashgear/action-check-pr-title@v5.0.1. 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: ashley-taylor/junit-report-annotations-action@f9c1a5cbe28479439f82b80a5402a6d3aa1990ac. 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/

A label component must be associated with a form element

Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly

Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly

Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly

Unexpected nullable string value in conditional. Please handle the nullish/empty cases explicitly

A label component must be associated with a form element

`statusText` is deprecated. With HTTP/2 and later versions, this will incorrectly remain set to 'OK' even when the status code of a response is not 200

A label component must be associated with a form element

A label component must be associated with a form element