chore: bump the npm-non-major group across 1 directory with 36 updates #3297
dependabot[bot]quality-checks.yml
on: pull_request
Format check
29s
Lint
22s
Typecheck
39s
Knip
29s
Tests
42s
Build
1m 26s
Annotations
11 errors and 16 warnings
|
jsx-a11y(control-has-associated-label):
src/app/pages/client/ClientNonUIFeatures.tsx#L236
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/components/user-profile/UserChips.tsx#L665
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/features/room/message/Message.tsx#L1227
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/features/settings/cosmetics/Themes.tsx#L295
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/features/settings/cosmetics/ThemeImportModal.tsx#L318
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/features/settings/cosmetics/ThemeImportModal.tsx#L299
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/features/room/poll-modals/PollDialog.tsx#L294
A control must be associated with a text label.
|
|
jsx-a11y(no-noninteractive-element-to-interactive-role):
src/app/components/message/RenderBody.tsx#L128
Non-interactive elements should not be assigned interactive roles.
|
|
jsx-a11y(control-has-associated-label):
src/app/components/ClientSideHoverFreeze.tsx#L62
A control must be associated with a text label.
|
|
jsx-a11y(control-has-associated-label):
src/app/components/upload-card/UploadCardRenderer.tsx#L88
A control must be associated with a text label.
|
|
Tests
Process completed with exit code 1.
|
|
Lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
eslint(no-underscore-dangle):
src/app/utils/delayedEvents.ts#L95
Unexpected dangling '_' in '`_unstable_updateDelayedEvent`'.
|
|
eslint(no-underscore-dangle):
src/app/utils/delayedEvents.ts#L91
Unexpected dangling '_' in '`_unstable_getDelayedEvents`'.
|
|
eslint(no-underscore-dangle):
src/app/utils/delayedEvents.ts#L81
Unexpected dangling '_' in '`_unstable_sendDelayedEvent`'.
|
|
eslint(no-underscore-dangle):
src/app/utils/delayedEvents.ts#L32
Unexpected dangling '_' in '`_unstable_sendDelayedEvent`'.
|
|
unicorn(consistent-function-scoping):
src/app/hooks/useMemberEventParser.tsx#L59
Function `parseMemberEvent` does not capture any variables from its parent scope
|
|
eslint(no-underscore-dangle):
src/app/hooks/useUserProfile.ts#L141
Unexpected dangling '_' in '`_fetched`'.
|
|
eslint(no-underscore-dangle):
src/app/hooks/useUserProfile.ts#L139
Unexpected dangling '_' in '`_fetched`'.
|
|
unicorn(consistent-function-scoping):
src/app/plugins/react-custom-html-parser.tsx#L396
Function `worker` does not capture any variables from its parent scope
|
|
unicorn(consistent-function-scoping):
src/app/components/image-pack-view/UsageSwitcher.tsx#L10
Function `getUsageStr` does not capture any variables from its parent scope
|
|
unicorn(consistent-function-scoping):
src/app/utils/room.ts#L794
Function `readReplaceTargetId` does not capture any variables from its parent scope
|
|
Knip
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Format check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Typecheck
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Tests
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|
|
Build
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@b906affcce14559ad1aafd4ab0e942779e9f58b1. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/
|