update SDL version #665
electronstudioAnnotations
145 errors and 66 warnings
|
build-mac-arm64 (3.14, Desktop)
Process completed with exit code 1.
|
|
build-mac-arm64 (3.12, SDL)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.10, Desktop)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.10, SDL)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.14, SDL)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.12, Desktop)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.13, SDL)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.11, SDL)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.13, Desktop)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-mac-arm64 (3.11, Desktop)
The strategy configuration was canceled because "build-mac-arm64._3_14_Desktop" failed
|
|
build-linux-arm64 (3.10, DRM)
Process completed with exit code 1.
|
|
build-linux-arm64 (3.10, SDL)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.14, SDL)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.12, DRM)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.13, DRM)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.12, SDL)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.11, Desktop)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.13, Desktop)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.14, DRM)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux32 (python3.7, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.7, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.7, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.13, DRM)
Process completed with exit code 1.
|
|
build-linux-arm64 (3.14, Desktop)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.14, Desktop)
The operation was canceled.
|
|
build-linux32 (python3.9, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.10, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.10, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.12, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.9, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.8, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.8, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.12, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.8, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.9, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.11, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux-arm64 (3.13, SDL)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.13, SDL)
The operation was canceled.
|
|
build-linux32 (python3.11, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.13, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.11, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.13, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.14, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.14, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.12, Desktop)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.14, DRM)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux-arm64 (3.10, Desktop)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.10, Desktop)
The operation was canceled.
|
|
build-linux-arm64 (3.12, Desktop)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.12, Desktop)
The operation was canceled.
|
|
build-linux-arm64 (3.11, SDL)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.11, SDL)
The operation was canceled.
|
|
build-linux-arm64 (3.11, DRM)
The strategy configuration was canceled because "build-linux-arm64._3_10_DRM" failed
|
|
build-linux-arm64 (3.11, DRM)
The operation was canceled.
|
|
build-linux32 (python3.10, SDL)
The strategy configuration was canceled because "build-linux32.python3_13_DRM" failed
|
|
build-linux32 (python3.10, SDL)
The operation was canceled.
|
|
build-linux (python3.12, Desktop)
Process completed with exit code 1.
|
|
build-linux (python3.7, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.7, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.8, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.10, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.7, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.8, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.9, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.8, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.9, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.9, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.11, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.9, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.11, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.8, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.10, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.10, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.11, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.13, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.14, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.12, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.12, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.13, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.13, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.12, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.11, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (pypy3.11, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.10, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.14, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.14, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (pypy3.11, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.13, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.14, SDL)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (pypy3.11, Desktop)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (pypy3.11, DRM)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.7, SDL_SOFT)
The strategy configuration was canceled because "build-linux.python3_12_Desktop" failed
|
|
build-linux (python3.7, SDL_SOFT)
The operation was canceled.
|
|
build-mac-intel (3.7, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.8, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.11, SDL)
Process completed with exit code 1.
|
|
build-mac-intel (3.10, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.9, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.9, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.14, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.14, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.13, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.13, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.12, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.10, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (pypy-3.11, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (pypy-3.11, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.7, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.7, SDL)
Process completed with exit code 1.
|
|
build-mac-intel (3.12, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.12, SDL)
The operation was canceled.
|
|
build-mac-intel (3.8, SDL)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.8, SDL)
Process completed with exit code 1.
|
|
build-mac-intel (3.11, Desktop)
The strategy configuration was canceled because "build-mac-intel._3_11_SDL" failed
|
|
build-mac-intel (3.11, Desktop)
Process completed with exit code 1.
|
|
build-windows (3.9, Desktop)
The run was canceled by @electronstudio.
|
|
build-windows (pypy-3.11, Desktop)
The run was canceled by @electronstudio.
|
|
build-windows (pypy-3.11, Desktop)
The operation was canceled.
|
|
build-windows (3.8, SDL)
The run was canceled by @electronstudio.
|
|
build-windows (3.8, SDL)
The operation was canceled.
|
|
build-windows (3.7, Desktop)
The run was canceled by @electronstudio.
|
|
build-windows (3.7, Desktop)
The operation was canceled.
|
|
build-windows (pypy-3.11, SDL_SOFT)
The run was canceled by @electronstudio.
|
|
build-windows (pypy-3.11, SDL_SOFT)
The operation was canceled.
|
|
build-windows (pypy-3.11, SDL)
The run was canceled by @electronstudio.
|
|
build-windows (pypy-3.11, SDL)
The operation was canceled.
|
|
build-windows (3.9, SDL)
The run was canceled by @electronstudio.
|
|
build-windows (3.9, SDL)
The operation was canceled.
|
|
build-windows (3.8, SDL_SOFT)
The run was canceled by @electronstudio.
|
|
build-windows (3.8, SDL_SOFT)
The operation was canceled.
|
|
build-windows (3.8, Desktop)
The run was canceled by @electronstudio.
|
|
build-windows (3.8, Desktop)
The operation was canceled.
|
|
build-windows32 (3.11, SDL)
The run was canceled by @electronstudio.
|
|
build-windows32 (3.11, SDL)
The operation was canceled.
|
|
build-windows (3.11, SDL)
The run was canceled by @electronstudio.
|
|
build-windows (3.11, SDL)
The operation was canceled.
|
|
build-windows (3.11, SDL_SOFT)
The run was canceled by @electronstudio.
|
|
build-windows (3.14, SDL)
The run was canceled by @electronstudio.
|
|
build-windows (3.11, SDL_SOFT)
The operation was canceled.
|
|
build-windows (3.14, SDL)
The operation was canceled.
|
|
build-windows (3.10, SDL)
The run was canceled by @electronstudio.
|
|
build-windows (3.10, SDL)
The operation was canceled.
|
|
build-windows (3.13, Desktop)
The run was canceled by @electronstudio.
|
|
build-windows (3.13, Desktop)
The operation was canceled.
|
|
Build
The run was canceled by @electronstudio.
|
|
build-mac-arm64 (3.14, Desktop)
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. 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/
|
|
dynamic-distro
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/setup-python@v5, actions/upload-artifact@v4. 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/
|
|
source-distro
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/setup-python@v5, actions/upload-artifact@v4. 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/
|
|
build-linux-arm64 (3.10, DRM)
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. 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-linux-arm64 (3.14, Desktop)
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. 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-linux-arm64 (3.13, SDL)
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. 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-linux-arm64 (3.10, Desktop)
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. 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-linux-arm64 (3.12, Desktop)
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. 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-linux-arm64 (3.11, SDL)
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. 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-linux-arm64 (3.11, DRM)
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. 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-windows32 (3.7, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.13, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.9, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.12, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.11, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.10, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.9, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.14, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.7, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.8, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.7, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.12, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.9, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.10, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.10, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.8, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.12, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.13, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.14, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.14, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.12, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.11, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.13, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.13, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.14, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.7, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.11, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.14, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-mac-intel (3.11, SDL)
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. 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-mac-intel (3.7, SDL)
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. 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-mac-intel (3.12, SDL)
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. 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-mac-intel (3.8, SDL)
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. 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-mac-intel (3.11, Desktop)
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. 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-windows (3.7, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.8, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.12, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.10, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.12, SDL)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.10, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.13, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.9, SDL_SOFT)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.9, Desktop)
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/setup-python@v5, actions/upload-artifact@v4, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (pypy-3.11, Desktop)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.8, SDL)
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/setup-python@v5. 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/
|
|
build-windows (3.7, Desktop)
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/setup-python@v5. 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/
|
|
build-windows (pypy-3.11, SDL_SOFT)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (pypy-3.11, SDL)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.9, SDL)
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/setup-python@v5. 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/
|
|
build-windows (3.8, SDL_SOFT)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.8, Desktop)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows32 (3.11, SDL)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.11, SDL)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.11, SDL_SOFT)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.14, SDL)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.10, SDL)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
|
build-windows (3.13, Desktop)
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/setup-python@v5, microsoft/setup-msbuild@v2. 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/
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
wheel-dynamic
|
3.02 MB |
sha256:9ac7b741effa3b733896746a3e370cb07824ed34ff19c8bfefc567f42dc770c0
|
|
|
wheel-source
|
184 KB |
sha256:89d8bd81e08ff4c54f098a1395d3c0361bee66e7812453fc0c664b36c835d341
|
|
|
wheel-windows-Desktop-3.10
|
2.2 MB |
sha256:a40a1a8d368f5f180ce0070d39d30442acb60ad4c63addff55a2545fd8f1e9bd
|
|
|
wheel-windows-Desktop-3.11
|
2.2 MB |
sha256:a781ffd6819752de49a8dc5175dcccf5c296a9416ad0a9b63c8e76ce7cdd2310
|
|
|
wheel-windows-Desktop-3.12
|
2.2 MB |
sha256:be3b051dfd0a3f3870fbb0370ef246347475306e6f8b5ab81de29470310e26d1
|
|
|
wheel-windows-Desktop-3.14
|
2.28 MB |
sha256:5517875c86120b27e8e6a6b7b8eb0e47256d0de35c2d648597b9b4fe78cbcdde
|
|
|
wheel-windows-Desktop-3.9
|
2.2 MB |
sha256:51eae821e31116e71db8fb86a71f19426e5453d1007669d10d672b4e0bdfa4f2
|
|
|
wheel-windows-SDL-3.12
|
2.12 MB |
sha256:4394990c223ecf235ac9f849cad00585fba8fc405493b0e5baf64f0366fb24e5
|
|
|
wheel-windows-SDL-3.13
|
2.12 MB |
sha256:7569e31d6737234cd5c862a913e03e8012913b0432f2501b3328da0d4c0826ce
|
|
|
wheel-windows-SDL-3.7
|
2.12 MB |
sha256:1d40ca4ef52bfa8e603e30e16b2b0133afd8be4c7846e96a597ccc2dda9c59b8
|
|
|
wheel-windows-SDL_SOFT-3.10
|
2.11 MB |
sha256:a68f90fbcebb321c92a9e602276f81a26b0ebac2705c4ea7486cf6a8c52623f9
|
|
|
wheel-windows-SDL_SOFT-3.12
|
2.12 MB |
sha256:69b79f52bb71642d435b1d10cf6279643191d1dd30a6f421b4403eb4f3a4f944
|
|
|
wheel-windows-SDL_SOFT-3.13
|
2.12 MB |
sha256:e447dee5cda6cc66fbad371c8b18b1a47adc7c4dc04b8f14669d435472b55056
|
|
|
wheel-windows-SDL_SOFT-3.14
|
2.19 MB |
sha256:1bc038b2c08f7aead166171c3d2a4931f67492fe60397944edab422577706dc9
|
|
|
wheel-windows-SDL_SOFT-3.7
|
2.11 MB |
sha256:80ab86ed6b6d4bf1d8e5759b38185e65cc4cb83db7270dc5d7a2b4c7bc6af7cd
|
|
|
wheel-windows-SDL_SOFT-3.9
|
2.11 MB |
sha256:9c2216227f496d919fe7ad57d4e57a348209bf7f45c7425252c4e21b9ac06408
|
|
|
wheel-windows32-Desktop-3.10
|
1.87 MB |
sha256:2767a505d36be5d50bf452913f9f1ab147be67baadc74505d5d849239353e4ae
|
|
|
wheel-windows32-Desktop-3.11
|
1.87 MB |
sha256:56a5b542ff36cb2e929113771f8215f3739ff9123c99f9e17e9222aa51c47813
|
|
|
wheel-windows32-Desktop-3.12
|
1.87 MB |
sha256:eac41126a3ef1a583729caad7f4c24f0d8009cfc5cf674aae89eda499a4f2062
|
|
|
wheel-windows32-Desktop-3.13
|
1.87 MB |
sha256:fbdda3f41eb00670224bec9f4da70547d6e9373bee44f94eafed4710deda7a1b
|
|
|
wheel-windows32-Desktop-3.14
|
1.92 MB |
sha256:095d37e497061a9e62453eebf3e4f9e5f666a979e51cf2d13853d6495f5101ad
|
|
|
wheel-windows32-Desktop-3.7
|
1.87 MB |
sha256:71aa146038e1b535e57649b828de36f523fed9acd7815fb75bf0685fe9c42592
|
|
|
wheel-windows32-Desktop-3.8
|
1.87 MB |
sha256:603906d3e336e44361dade9f8802ffcbf03d71ffd42a9779d04a21b0b62d407f
|
|
|
wheel-windows32-Desktop-3.9
|
1.87 MB |
sha256:c4e827023ddc3d6d80ba869a008db1c231df490a6942f878da59ea0a937c2ebe
|
|
|
wheel-windows32-SDL-3.10
|
1.8 MB |
sha256:452c802e1831172d6f79dc29eb935acdbd560fa371beaa65aab3d2350b6d02ea
|
|
|
wheel-windows32-SDL-3.12
|
1.8 MB |
sha256:d8e3074bb9a589164bbdc0bbbd7813bccb154cfa67a93c3a7604b30159b6a2d9
|
|
|
wheel-windows32-SDL-3.13
|
1.8 MB |
sha256:c844a848f9083fcdcfc1830eba17324e9282238a99d22eeec924ded8b239fb4a
|
|
|
wheel-windows32-SDL-3.14
|
1.85 MB |
sha256:c24aea7a0dcf2246ba5034ac5e222d0b57eeb14ffb47563d6762013b4a559c6d
|
|
|
wheel-windows32-SDL-3.7
|
1.8 MB |
sha256:6372fab63f6886e536333efc03eddca038369a1bbb31677b3e008ab91c1f04fe
|
|
|
wheel-windows32-SDL-3.8
|
1.8 MB |
sha256:1d4f79f1a4f5660404edf4cd5dcd36c8c0bfaaee752764bae482ad1992767304
|
|
|
wheel-windows32-SDL-3.9
|
1.8 MB |
sha256:f6feedf68d45b332b47551cafdd40806720e0ed8b1d5ea65b19c6f7d8642a042
|
|
|
wheel-windows32-SDL_SOFT-3.10
|
1.79 MB |
sha256:ac01e095a3ce08b16fe16c6e5d4637f688b761b2b812b06244c534ebdaec1101
|
|
|
wheel-windows32-SDL_SOFT-3.11
|
1.79 MB |
sha256:48c2571521c1f438ccbc5dceeb83cd2b013eff63779006add0704fa1cd22aecb
|
|
|
wheel-windows32-SDL_SOFT-3.12
|
1.79 MB |
sha256:89c39736289bb4b2a8b7fcb4ae943cbbfe38d52c9641eb45c30bdedfcb217b76
|
|
|
wheel-windows32-SDL_SOFT-3.13
|
1.79 MB |
sha256:8f4bd869ab88bc507a952d79ba4e1ce598d4157e380b1584a044b704e7ac97ea
|
|
|
wheel-windows32-SDL_SOFT-3.14
|
1.84 MB |
sha256:cfce29720b357b378298672002005e22b3af0eee13c9cfdeb646e5891d5ba04c
|
|
|
wheel-windows32-SDL_SOFT-3.7
|
1.79 MB |
sha256:590e440b434cf35470164256e8f1f246d160470e37284237c12eb69c0cad881d
|
|
|
wheel-windows32-SDL_SOFT-3.8
|
1.79 MB |
sha256:ba182046cc117717f4bff9e8dcdb7873f7e224bf80b132065e8d9fde4671b797
|
|
|
wheel-windows32-SDL_SOFT-3.9
|
1.79 MB |
sha256:301314f21d5e490c9df5593f876dcc7147943dade7c0a1ab2c49cd25740073e2
|
|