Skip to content

Use IModel in the public API. #664

Use IModel in the public API.

Use IModel in the public API. #664

Triggered via pull request March 31, 2026 07:03
Status Success
Total duration 37m 30s
Artifacts 24

foundry-local-sdk-build.yml

on: pull_request
build-cs-windows  /  build
3m 26s
build-cs-windows / build
build-js-windows  /  build
3m 26s
build-js-windows / build
build-python-windows  /  build
2m 49s
build-python-windows / build
build-rust-windows  /  build
3m 11s
build-rust-windows / build
build-cs-windows-WinML  /  build
4m 33s
build-cs-windows-WinML / build
build-js-windows-WinML  /  build
2m 30s
build-js-windows-WinML / build
build-python-windows-WinML  /  build
2m 44s
build-python-windows-WinML / build
build-rust-windows-WinML  /  build
3m 27s
build-rust-windows-WinML / build
build-cs-macos  /  build
1m 30s
build-cs-macos / build
build-js-macos  /  build
2m 1s
build-js-macos / build
build-python-macos  /  build
1m 55s
build-python-macos / build
build-rust-macos  /  build
2m 5s
build-rust-macos / build
Fit to window
Zoom out
Zoom in

Annotations

12 warnings
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-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-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-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-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-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-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-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-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-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-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-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/

Artifacts

Produced during runtime
Name Size Digest
cs-sdk-macos
287 KB
sha256:a4c99be3240cfb5f7d8ee69f47f0a0536b7302f82d56054692536e2e04f73bed
cs-sdk-macos-logs
11.9 KB
sha256:1c8afadcd423712f0fa86b4ea3d64cfd03bc9adb3eba9f259f8cda57995a967d
cs-sdk-windows
287 KB
sha256:1f8f98c178ba0e39249963b202a066eaf350f286501f8cfa137de95a1857cc64
cs-sdk-windows-logs
12.5 KB
sha256:e326a4f5c321779548cef1eb49f1fba162d46c16e0123e3c8f19336fc0bd65a2
cs-sdk-windows-winml
301 KB
sha256:895242734cbe72e90cb28f1dca06dc4b8082e462d1d7652465a5d40431b33538
cs-sdk-windows-winml-logs
11.1 KB
sha256:c28901c3b2cf373bacb34d836a137493f6c769036ce54f924498ad0f7dd96925
js-sdk-macos
20 KB
sha256:fcfd9fae3341a34eab186c43231ddae5f61f16177477079d77528847781fc7d5
js-sdk-macos-logs
399 Bytes
sha256:40c618da0418e6c2ff45da602c973d75aa2033a7d1c98cd4501fbf9b35bdde9c
js-sdk-windows
20.1 KB
sha256:ed53374d4eb1967950341cc76f808df0295cecf39d4651a4251778f61b81e38e
js-sdk-windows-logs
394 Bytes
sha256:ee2b2340cfd41408ce8304cc935041b0b99d87db8b786fa392130c617265269b
js-sdk-windows-winml
20.1 KB
sha256:7ffaa587ef74e32a2314d9d2f3735b98ff9985e16a9669321c132d66e5bebf71
js-sdk-windows-winml-logs
394 Bytes
sha256:9e7ed5b6c33e18c170db029afdbf138737aa9c5f6d4aa58f55a6f12402d3f041
python-sdk-macos
30.4 KB
sha256:cc43726bc790cb61bb368d337ab2ef64e847ec282442c8e643743aaae3e26b10
python-sdk-macos-logs
404 Bytes
sha256:3dbf90b5375ac119ff5ea99234c018f0932ae562c7f9a97394ac216eca82433f
python-sdk-windows
30.7 KB
sha256:4ed672eb6d2ce5111bb66b57edab234554f950bf1ac1c23227183520d786ee7b
python-sdk-windows-logs
401 Bytes
sha256:ad6cd9f1f2bcb538232efb973621404346df414bab68068db2ef1f93250aa785
python-sdk-windows-winml
30.7 KB
sha256:9e3c6ed8fe93d69ec2d44b482f17392b53d76a5b25ded9ae7f5f66247e7e4091
python-sdk-windows-winml-logs
401 Bytes
sha256:c44f00e13b1b07eb6d910652efaa89325ad5828afe55b191a9cbf0577a5543b0
rust-sdk-macos
56.5 KB
sha256:13e39141808a547ba7632293e2dafc7a4a81fdd00c49501a1f30b09c216ccfad
rust-sdk-macos-logs
387 Bytes
sha256:e6fa4eb3b886b17432d7fd89706cc1592cb650ddbb953dff0e04ae7b88bc8e90
rust-sdk-windows
56.8 KB
sha256:1aa943d4226cfcdb1403ac8551035eb3938acbd5eede84e120343dfd4091ad3f
rust-sdk-windows-logs
385 Bytes
sha256:26bc033af4a2923c9b94a9b9118d5ec7bd7debeecf3a637de7c9fa1eb757c525
rust-sdk-windows-winml
56.8 KB
sha256:9c126043b87268e8ea07b6c6092cfd946d19af99b0cc70f4f794fedfb68020c2
rust-sdk-windows-winml-logs
384 Bytes
sha256:7507282da0218849570855d6e8fe5272821d2b1d3c13dd0844e1c53154503b77