fix: select defaultValue re-render issue #8996
canerakdaslint-and-tests.yml
on: pull_request
Quality checks
2m 48s
Tests
1m 16s
Annotations
3 warnings and 4 notices
|
Tests
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, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda, step-security/harden-runner@f4a75cfd619ee5ce8d5b864b0d183aff3c69b55a. 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/
|
|
Quality checks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda, step-security/harden-runner@f4a75cfd619ee5ce8d5b864b0d183aff3c69b55a. 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/
|
|
Quality checks:
packages/ui-components/src/Common/Select/index.tsx#L67
Do not call the 'set' function 'setValue' of 'useState' synchronously in an effect. This can lead to unnecessary re-renders and performance issues
|
|
Tests
Total Tests: 157
Suites 📂: 48
Passed ✅: 157
Failed ❌: 0
Canceled 🚫: 0
Skipped ⏭️: 0
Todo 📝: 0
Duration 🕐: 30910.224ms
|
|
Tests
Total Tests: 35
Suites 📂: 15
Passed ✅: 35
Failed ❌: 0
Canceled 🚫: 0
Skipped ⏭️: 0
Todo 📝: 0
Duration 🕐: 18741.071ms
|
|
Tests
Total Tests: 58
Suites 📂: 9
Passed ✅: 58
Failed ❌: 0
Canceled 🚫: 0
Skipped ⏭️: 0
Todo 📝: 0
Duration 🕐: 1985.665ms
|
|
Tests
Total Tests: 4
Suites 📂: 4
Passed ✅: 4
Failed ❌: 0
Canceled 🚫: 0
Skipped ⏭️: 0
Todo 📝: 0
Duration 🕐: 721.805ms
|