Fix new Window callbacks not being triggered #232
Raltyromain.yml
on: pull_request
package-haxelib
11s
Matrix: unit-test-air
Matrix: unit-test-hashlink
Matrix: unit-test-neko
unit-test-lime-develop
13m 29s
Matrix: neko-samples
html5-samples
1m 19s
flash-samples
24s
hashlink-samples
25s
notify
0s
Annotations
34 errors and 23 warnings
|
unit-test-neko (4.2.5)
Process completed with exit code 1.
|
|
unit-test-neko (4.3.6)
The strategy configuration was canceled because "unit-test-neko._4_2_5" failed
|
|
unit-test-neko (4.3.6)
The operation was canceled.
|
|
neko-samples (4.3.6)
Process completed with exit code 1.
|
|
flash-samples
Process completed with exit code 1.
|
|
unit-test-neko (4.0.5)
The strategy configuration was canceled because "unit-test-neko._4_2_5" failed
|
|
unit-test-neko (4.0.5)
The operation was canceled.
|
|
docs
Process completed with exit code 1.
|
|
unit-test-hashlink (4.3.6)
Process completed with exit code 1.
|
|
neko-samples (4.1.5)
The strategy configuration was canceled because "neko-samples._4_3_6" failed
|
|
neko-samples (4.1.5)
The operation was canceled.
|
|
unit-test-neko-haxe3
Process completed with exit code 1.
|
|
neko-samples (4.0.5)
The strategy configuration was canceled because "neko-samples._4_3_6" failed
|
|
neko-samples (4.0.5)
The operation was canceled.
|
|
hashlink-samples
Process completed with exit code 1.
|
|
neko-samples (3.4.7)
The strategy configuration was canceled because "neko-samples._4_3_6" failed
|
|
unit-test-neko (4.1.5)
The strategy configuration was canceled because "unit-test-neko._4_2_5" failed
|
|
neko-samples (3.4.7)
The operation was canceled.
|
|
unit-test-neko (4.1.5)
The operation was canceled.
|
|
neko-samples (4.2.5)
The strategy configuration was canceled because "neko-samples._4_3_6" failed
|
|
neko-samples (4.2.5)
The operation was canceled.
|
|
unit-test-hashlink (4.2.5)
The strategy configuration was canceled because "unit-test-hashlink._4_3_6" failed
|
|
unit-test-hashlink (4.2.5)
The operation was canceled.
|
|
unit-test-air (4.0.5)
Process completed with exit code 1.
|
|
html5-samples
Process completed with exit code 1.
|
|
unit-test-air (3.4.7)
The strategy configuration was canceled because "unit-test-air._4_0_5" failed
|
|
unit-test-air (3.4.7)
The operation was canceled.
|
|
unit-test-air (4.3.6)
The strategy configuration was canceled because "unit-test-air._4_0_5" failed
|
|
unit-test-air (4.3.6)
The operation was canceled.
|
|
unit-test-air (4.2.5)
The strategy configuration was canceled because "unit-test-air._4_0_5" failed
|
|
unit-test-air (4.2.5)
The operation was canceled.
|
|
unit-test-air (4.1.5)
The strategy configuration was canceled because "unit-test-air._4_0_5" failed
|
|
unit-test-air (4.1.5)
The operation was canceled.
|
|
unit-test-lime-develop
Process completed with exit code 1.
|
|
package-haxelib
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-neko (4.2.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-neko (4.3.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
neko-samples (4.3.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
flash-samples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-neko (4.0.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
docs
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-hashlink (4.3.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
neko-samples (4.1.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-neko-haxe3
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
neko-samples (4.0.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
hashlink-samples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
neko-samples (3.4.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-neko (4.1.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
neko-samples (4.2.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-hashlink (4.2.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-air (4.0.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: joshtynjala/setup-adobe-air-action@v2, krdlab/setup-haxe@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/
|
|
html5-samples
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: krdlab/setup-haxe@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/
|
|
unit-test-air (3.4.7)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: joshtynjala/setup-adobe-air-action@v2, krdlab/setup-haxe@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/
|
|
unit-test-air (4.3.6)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: joshtynjala/setup-adobe-air-action@v2, krdlab/setup-haxe@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/
|
|
unit-test-air (4.2.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: joshtynjala/setup-adobe-air-action@v2, krdlab/setup-haxe@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/
|
|
unit-test-air (4.1.5)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: joshtynjala/setup-adobe-air-action@v2, krdlab/setup-haxe@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/
|
|
unit-test-lime-develop
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: joshtynjala/setup-adobe-air-action@v2, krdlab/setup-haxe@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 | |
|---|---|---|---|
|
openfl-haxelib
Expired
|
2.86 MB |
sha256:ec34d9d9c69e74f60c443003374b22904a6a5a228cc0e903e05e84b204769ac2
|
|