Skip to content

Added support to VTK file reader to read appended data with zlib comp… #722

Added support to VTK file reader to read appended data with zlib comp…

Added support to VTK file reader to read appended data with zlib comp… #722

Triggered via push March 24, 2026 21:27
Status Success
Total duration 18m 27s
Artifacts 2

windows-push.yml

on: push
call_workflow  /  Start self-hosted EC2 runner
6m 46s
call_workflow / Start self-hosted EC2 runner
call_workflow  /  Clone and build
10m 24s
call_workflow / Clone and build
call_workflow  /  Run test suite
0s
call_workflow / Run test suite
call_workflow  /  Upload artifacts to repo
17s
call_workflow / Upload artifacts to repo
call_workflow  /  Publish to S3
15s
call_workflow / Publish to S3
call_workflow  /  Stop self-hosted EC2 runner
1m 10s
call_workflow / Stop self-hosted EC2 runner
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
call_workflow / Start self-hosted EC2 runner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4, febiosoftware/ec2-multiple-github-runners@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_workflow / Clone and build
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/upload-artifact@v4, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_workflow / Publish to S3
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/download-artifact@v4, aws-actions/configure-aws-credentials@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_workflow / Upload artifacts to repo
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/download-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
call_workflow / Stop self-hosted EC2 runner
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: aws-actions/configure-aws-credentials@v4, febiosoftware/ec2-multiple-github-runners@main. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
febio-studio-Windows-X64
13.4 MB
sha256:7c1432cc999796dd7ee02213dc8c25ac6eefad4979cfb14cd626780aa43bfac5
febio-studio-updater-Windows-X64
1.04 MB
sha256:39c99b62d9a465e7ba479fc729035a97a4b5de4d065646021cfa5c592f2c34d5