Skip to content
PR Release Tests

Just run the tests here #149

Sign in to view logs

Just run the tests here

Just run the tests here #149

Triggered via pull request April 4, 2026 10:48
@florianPatflorianPat
synchronize #10
flos_core
Status Success
Total duration 4m 25s
Artifacts 8

pr-release-tests.yml

on: pull_request
Matrix: package
verify  /  generate-checksums
8s
verify / generate-checksums
release
22s
release
Matrix: npm
Fit to window
Zoom out
Zoom in

Annotations

7 warnings and 6 notices
package (arm64, win) / pkg-binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v4, lando/prepare-release-action@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/
package (arm64, linux) / pkg-binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v4, lando/prepare-release-action@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/
package (arm64, macos) / pkg-binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v4, lando/prepare-release-action@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/
package (x64, macos) / pkg-binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v4, lando/prepare-release-action@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/
package (x64, win) / pkg-binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v4, lando/prepare-release-action@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/
package (x64, linux) / pkg-binary
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v4, lando/prepare-release-action@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/
npm (20)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: lando/prepare-release-action@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/
pkg installed
Using version 5.16.1
pkg installed
Using version 5.16.1
pkg installed
Using version 5.16.1
pkg installed
Using version 5.16.1
pkg installed
Using version 5.16.1
pkg installed
Using version 5.16.1

Artifacts

Produced during runtime
Name Size Digest
checksums-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
447 Bytes
sha256:80be5c63d3d73148b542808afd472c8b5f287976b96c1c886782097aa33ea66f
packaged-lando-linux-arm64-a9ccbab40fd161054d947b55d467a0d851766f7a-linux-arm64-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
34.2 MB
sha256:dd04897684ca04e1966eae482d3402157a685decf68860d100b53b37378ada59
packaged-lando-linux-x64-a9ccbab40fd161054d947b55d467a0d851766f7a-linux-x64-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
34.8 MB
sha256:739dee58d6e6122a9b04a3c273f38ce9e01be1093e6121a5f75178850c48a865
packaged-lando-macos-arm64-a9ccbab40fd161054d947b55d467a0d851766f7a-macos-arm64-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
33.4 MB
sha256:d9cdd5e69eab7eb05b46f7e8b2e7578091dbbb092dbf226da1711af3db387580
packaged-lando-macos-x64-a9ccbab40fd161054d947b55d467a0d851766f7a-macos-x64-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
34.2 MB
sha256:dad300d736a2644a315058721f0faea276a5800f8ebab50d942a397c24d73fc8
packaged-lando-win-arm64-a9ccbab40fd161054d947b55d467a0d851766f7a-win-arm64-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
24.6 MB
sha256:17460ac028920a45617a8a9cb3bdd89724dbb6542f6bb4c59c882a482b7deebd
packaged-lando-win-x64-a9ccbab40fd161054d947b55d467a0d851766f7a-win-x64-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
30.5 MB
sha256:c8abc1063adb8ce26733afd8b5d6a32a484f6f3d3c5a8d3aaaf4401990a9848f
pr-release-test-a9ccbab40fd161054d947b55d467a0d851766f7a Expired
192 MB
sha256:0579fe06830ce3d0d374656f384fe54d2e755663b08b0c36f460799784af639a