Skip to content

implement ADO packaging pipeline for FLC & SDK #629

implement ADO packaging pipeline for FLC & SDK

implement ADO packaging pipeline for FLC & SDK #629

Triggered via pull request March 29, 2026 22:38
Status Success
Total duration 4m 14s
Artifacts 24

foundry-local-sdk-build.yml

on: pull_request
build-cs-windows  /  build
3m 49s
build-cs-windows / build
build-js-windows  /  build
2m 20s
build-js-windows / build
build-python-windows  /  build
2m 59s
build-python-windows / build
build-rust-windows  /  build
3m 38s
build-rust-windows / build
build-cs-windows-WinML  /  build
4m 3s
build-cs-windows-WinML / build
build-js-windows-WinML  /  build
2m 50s
build-js-windows-WinML / build
build-python-windows-WinML  /  build
3m 11s
build-python-windows-WinML / build
build-rust-windows-WinML  /  build
3m 51s
build-rust-windows-WinML / build
build-cs-macos  /  build
1m 43s
build-cs-macos / build
build-js-macos  /  build
1m 30s
build-js-macos / build
build-python-macos  /  build
1m 43s
build-python-macos / build
build-rust-macos  /  build
2m 22s
build-rust-macos / build
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
build-js-macos / 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/setup-node@v4, 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-cs-macos / 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. 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-python-macos / 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/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-js-windows / 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/setup-node@v4, 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-rust-macos / 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. 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-js-windows-WinML / 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/setup-node@v4, 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-python-windows / 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/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-python-windows-WinML / 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/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-rust-windows / 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. 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-rust-windows-WinML / 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. 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-cs-windows / 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. 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-cs-windows-WinML / 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. 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
cs-sdk-macos
291 KB
sha256:ab9c7fc895c37bccaf2e1efa12024f980d9b07b31c741bd2473cb6f29a0e9e98
cs-sdk-macos-logs
11.7 KB
sha256:2a3153c87b8c81b606983f1915d6d4d04bdc4b7d44b2fb85d28b3ab5f626a273
cs-sdk-windows
292 KB
sha256:f738514c7e5c8ebafd38d9660eb9729cf4737756a96c5d98d20e9f065ff546fb
cs-sdk-windows-logs
11.2 KB
sha256:6e9ad314f0ccbf3a0a829b6913b73c4264a1384c6937b4747ab8a0cfdc9eb4fd
cs-sdk-windows-winml
306 KB
sha256:8b6f5ca62e88d244416947b88250875c7af59cf8bcad834f8ccb00d1bfa20448
cs-sdk-windows-winml-logs
11.5 KB
sha256:d19116e67ceb46821303635f7d2be783ef1a2733e652ff7448e9ac3b9a2d8d41
js-sdk-macos
20.2 KB
sha256:b1edd8a9ecdd3285654e39a682e2ae389ac001193a29a2b52c18108d3ccba703
js-sdk-macos-logs
398 Bytes
sha256:4836f12ede116e8f9c90bdf1c8335c63379676e3d44270264cca101cd246ef47
js-sdk-windows
20.3 KB
sha256:92d50339c75b1e7936534c98a1be828149c0b89eddf63009a83e3819980c1f2a
js-sdk-windows-logs
394 Bytes
sha256:691595450f02a79506a0f54f57320022184344e0a52ea35bd0b7e06b0b2f0739
js-sdk-windows-winml
20.3 KB
sha256:79e23e49850aa208730fa30516bf6cbeb3303daec738d3c351e4cd42006940c7
js-sdk-windows-winml-logs
394 Bytes
sha256:375cb5e9852d876326f3d846487986069e342c41b6a00ae9990a8b57e391cc7a
python-sdk-macos
29.6 KB
sha256:26ba0d87562cd9dc690948dbc26fb63e43e6de076200dd4febad15f6128ac235
python-sdk-macos-logs
404 Bytes
sha256:ae3555f17ba480552b9c93a67517eca006b0167040cafb9167167a2e9a17331e
python-sdk-windows
29.9 KB
sha256:f537113b919e3fdff2b3176b34717bad30521c87ae643bf9c556e46b2004f596
python-sdk-windows-logs
399 Bytes
sha256:355af91f2857137644d984d6af01211dc63c95bb371225be0f48dda3cd4db1dc
python-sdk-windows-winml
29.9 KB
sha256:2eaeb8502cb426d379ac15044349d78e345a8f6e18c89bc0d87f716ec57a4f6e
python-sdk-windows-winml-logs
400 Bytes
sha256:c0b02bd66baec007999d3984569a5d9a6dbf01059cdec664a6a7cc5c7bc9c3f3
rust-sdk-macos
56.5 KB
sha256:02a32aa5fde0232dc7204037ae22ed42c163f1d5e85786f7e52f5525d600f957
rust-sdk-macos-logs
385 Bytes
sha256:736600143d67bb4def32a3a967e1f811e8562eed13219300b8f48f5d64deb02c
rust-sdk-windows
56.8 KB
sha256:dd5414a0de7626989493b04404e900c30ea9f5f39e08b72daa22de201fbdbc21
rust-sdk-windows-logs
384 Bytes
sha256:790fa8a84aee1fb0a0b2dbd565f0a5b291e0b25b760678345f518bad95bcec67
rust-sdk-windows-winml
56.8 KB
sha256:d247360d3ae1b758af369bc5da86eccf80e945a93d6ae59cddcf164bdf86cdb1
rust-sdk-windows-winml-logs
385 Bytes
sha256:b1acbfb3d063a00a2e520c25d2807eb20d0eec14ea3c1ec26c923d769ff9c959