feat: use frozen diff in use_dialog for efficient reactive updates #428
FeodorFitsnerAnnotations
23 errors and 8 warnings
|
Build (web-macos)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (macos)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (ipa)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (apk-macos)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (aab-macos)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (ios-simulator)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (linux)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (linux)
The operation was canceled.
|
|
Build (web-ubuntu)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (web-ubuntu)
The operation was canceled.
|
|
Build (aab-ubuntu)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (aab-ubuntu)
The operation was canceled.
|
|
Build (apk-ubuntu)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (apk-ubuntu)
The operation was canceled.
|
|
Build (aab-windows)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (aab-windows)
The operation was canceled.
|
|
Build (windows)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (windows)
The operation was canceled.
|
|
Build (apk-windows)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (apk-windows)
The operation was canceled.
|
|
Build (web-windows)
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (web-windows)
The operation was canceled.
|
|
Flet Build Test
Canceling since a higher priority waiting request for ci-Flet Build Test-declr-dialogs-api exists
|
|
Build (linux)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v6. 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/
|
|
Build (web-ubuntu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v6. 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/
|
|
Build (aab-ubuntu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, astral-sh/setup-uv@v6. 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/
|
|
Build (apk-ubuntu)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Build (aab-windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Build (windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Build (apk-windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|
|
Build (web-windows)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. 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/
|