whag #1291
msbuild.yml
on: push
build-android-x64
/
build-android-onearch
14m 7s
build-android-arm64
/
build-android-onearch
16m 7s
build-android-armv7
/
build-android-onearch
14m 54s
build-windows-x64
/
build-windows-onearch
2m 30s
build-windows-x86
/
build-windows-onearch
3m 34s
build-windows-arm64
/
build-windows-onearch
2m 40s
build-sdk
42s
build-linux64-flatpak
9m 45s
build-linux-appimage-x64
6m 54s
build-emscipten
5m 19s
android-merge-cpu-apks
26s
mac-merge-into-universal
21s
windows-post-under-older-url
6s
Annotations
19 warnings
|
build-sdk
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-x64 / build-windows-onearch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, microsoft/setup-msbuild@v1.0.2. 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-x64 / build-windows-onearch
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-windows-arm64 / build-windows-onearch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, microsoft/setup-msbuild@v1.0.2. 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-arm64 / build-windows-onearch
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-windows-x86 / build-windows-onearch
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, microsoft/setup-msbuild@v1.0.2. 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-x86 / build-windows-onearch
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
build-emscipten
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: mymindstorm/setup-emsdk@v14. 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-arm64
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-arm64
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
build-linux64-flatpak
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: flathub-infra/flatpak-github-actions/flatpak-builder@master. 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-x64
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-x64
jpeg-xl 0.11.2 is already installed and up-to-date.
To reinstall 0.11.2, run:
brew reinstall jpeg-xl
|
|
build-mac-x64
pkgconf 2.5.1 is already installed and up-to-date.
To reinstall 2.5.1, run:
brew reinstall pkgconf
|
|
mac-merge-into-universal
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-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-android-x64 / build-android-onearch
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-java@v3, android-actions/setup-android@v3. 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-android-armv7 / build-android-onearch
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-java@v3, android-actions/setup-android@v3. 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-android-arm64 / build-android-onearch
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-java@v3, android-actions/setup-android@v3. 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/
|
|
android-merge-cpu-apks
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v4, android-actions/setup-android@v3. 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 | |
|---|---|---|---|
|
voidsprite-build-android
|
29.3 MB |
sha256:fa9a5422ee1830741245bc98109c4fb4b05322d55b4cc3abddc2bc201860f508
|
|
|
voidsprite-build-android-arm64-v8a
Expired
|
15.8 MB |
sha256:77683d182994558386393cbc758c9e519a6f6d3c3f8463a2bc621f45acfd8165
|
|
|
voidsprite-build-android-armeabi-v7a
Expired
|
14.7 MB |
sha256:d8fba1608f060b4dd44d2e5f85174b09426e1e6d70b8d28d5ae25359922791d8
|
|
|
voidsprite-build-android-x86_64
Expired
|
15.7 MB |
sha256:a3fc652eb360288f433715a775bfdc16b38eb511f6626c99fadc7c7687e06dca
|
|
|
voidsprite-build-emscripten
|
9.67 MB |
sha256:f0a1206ed3cd672913815fdc3b32662d2f5425eef3bac3a9e12e9c65fa9c9d85
|
|
|
voidsprite-build-linux-appimage-x64
|
30.4 MB |
sha256:8468f41bb90060aad74faceb2870e1b8ee74f0591b41d0604471d665443748c5
|
|
|
voidsprite-build-linux64-flatpak-x86_64.flatpak
|
8.82 MB |
sha256:58d9860a687f8b1c4d1afd6e971d0a2c38803777bba91bf046a5ad71e384959d
|
|
|
voidsprite-build-mac-arm64
Expired
|
12.3 MB |
sha256:273966e127d39963f2cc60a1b7b4c504130c127c40b11ec71ae22080fd70676c
|
|
|
voidsprite-build-mac-intel64
Expired
|
12.9 MB |
sha256:82d6ae93f69200167d5972d40e21bef888acf4f30f3282a42bdd04bd0ef24a66
|
|
|
voidsprite-build-mac-universal
|
19 MB |
sha256:45777d7a865f5fe7bd0db85594d00ec3cc75433d862b2fd406a9db40f29a0b34
|
|
|
voidsprite-build-win-ARM64
|
14 MB |
sha256:e2157f162a1cc7b641018ae0fcf3fd8b6ee2cc52d30daa14f3f2e6a47afbe870
|
|
|
voidsprite-build-win-x64
|
16.2 MB |
sha256:adc41b43dabb5e8c3c8560a839f84551f6cb5add3d014188d6ffab93a8130114
|
|
|
voidsprite-build-win-x86
|
14.2 MB |
sha256:be486c5fa8b2206cea5c2f7c902ea76f08e6eef3066f0574b13a1382e2ebf414
|
|
|
voidsprite-build-win64.zip
|
16.2 MB |
sha256:adc41b43dabb5e8c3c8560a839f84551f6cb5add3d014188d6ffab93a8130114
|
|
|
voidsprite-sdk
|
2.2 KB |
sha256:1d711c15780b4b319d86e02df8c94fc1b923c61ee3e19576ed42b973ed488a66
|
|