implement ADO packaging pipeline for FLC & SDK #626
prathikrfoundry-local-sdk-build.yml
on: pull_request
build-cs-windows
/
build
2m 41s
build-js-windows
/
build
2m 28s
build-python-windows
/
build
2m 45s
build-rust-windows
/
build
3m 20s
build-cs-windows-WinML
/
build
3m 23s
build-js-windows-WinML
/
build
2m 22s
build-python-windows-WinML
/
build
2m 36s
build-rust-windows-WinML
/
build
3m 12s
build-cs-macos
/
build
1m 42s
build-js-macos
/
build
1m 28s
build-python-macos
/
build
1m 29s
build-rust-macos
/
build
2m 28s
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-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/
|
|
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-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-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-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-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-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-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:739845da771551dcfd4c1385260987cda10b2a886073857af3f784cee0a3dec9
|
|
|
cs-sdk-macos-logs
|
11.8 KB |
sha256:0e503cb7df0cf8084fb119a3c2bd10c87a1f5cdf36eef391a2cd20a3852dfd13
|
|
|
cs-sdk-windows
|
292 KB |
sha256:3f1a3fb99abfa0b19041badb7f8c6033ea270908b12c6bfbc97557c7362a1c88
|
|
|
cs-sdk-windows-logs
|
11.1 KB |
sha256:19a20501ededaa2a5dba2c4e7c398b9c9e21149861d589356fc1c81c148f20a6
|
|
|
cs-sdk-windows-winml
|
306 KB |
sha256:0a376af1af602113ec45c60468965e5fabfdf291d9e65b93338fc8ca61ecc17b
|
|
|
cs-sdk-windows-winml-logs
|
11.4 KB |
sha256:66ad3c819efc676541bc1497406a5a79edfbd07b8f4819ee2764d0c7efd0fb28
|
|
|
js-sdk-macos
|
20.2 KB |
sha256:edef0fb692159147d45ce63dd96e888589faebf793f22c9dcb006cefebad2cc7
|
|
|
js-sdk-macos-logs
|
399 Bytes |
sha256:d39c09a363d8bc31bdce2f0e7b4d838f1852d195ad9ad7f065867475e33f4633
|
|
|
js-sdk-windows
|
20.3 KB |
sha256:223ee227bb3960ce44706bd95706e83939f52582ba68e5fc37791e7b7b7a4ede
|
|
|
js-sdk-windows-logs
|
395 Bytes |
sha256:fa51522fbfb5b02191fe290b1eebd99e03c28a61bc16e65452668ac744d762ad
|
|
|
js-sdk-windows-winml
|
20.3 KB |
sha256:48662ecefcce3617ac6015809d89b5a55f046aba037c3fdf8a8e39ab6b68ddef
|
|
|
js-sdk-windows-winml-logs
|
394 Bytes |
sha256:4f6d27f81f089207c5e8cb69106885840a0101cebefb8f1e491318a5c0b43e30
|
|
|
python-sdk-macos
|
29.6 KB |
sha256:0bdc7522e32fc7d09d49b804d2646e4221fa4d7c3ce898a42ef5e4143e9f166f
|
|
|
python-sdk-macos-logs
|
405 Bytes |
sha256:a354656804028607f6852a6b734ac39f41582b770584f639a3a4b2a1de170737
|
|
|
python-sdk-windows
|
29.9 KB |
sha256:81ee71ee5d0f427b98bd57a6bde698bb563513ff14b007b7e55e4a4152acab38
|
|
|
python-sdk-windows-logs
|
402 Bytes |
sha256:ec97fb4126a6583b116c14f9f5069c954246d7b55444e033b72889e29ebe1bcc
|
|
|
python-sdk-windows-winml
|
29.9 KB |
sha256:7acbd1f0bef68e9fdf90ee978f35c698bef1704d0983a9c6700bb6d40e1d5270
|
|
|
python-sdk-windows-winml-logs
|
404 Bytes |
sha256:bc7f36e970a432a1e1ce6ed478347d4bdc3ce63203cd8212555741f109f90f69
|
|
|
rust-sdk-macos
|
56.5 KB |
sha256:fa19448ff7e31a9e1cc6c84c16cebc9236fb3ce50b3c75ba9d208896097661e9
|
|
|
rust-sdk-macos-logs
|
386 Bytes |
sha256:60cb4e5a787d65021f383e3abf42b8a1879feb4e7624b5f7b6459c8eb742549c
|
|
|
rust-sdk-windows
|
56.8 KB |
sha256:358b2a2f435540b89ac6a433180c784cd4bd8a8ef533071e1ec9fe8127c164b1
|
|
|
rust-sdk-windows-logs
|
385 Bytes |
sha256:0647d93e6ba3cb450042fa6d0bf540b9cb711fb9412ac806d49b50ae29724365
|
|
|
rust-sdk-windows-winml
|
56.8 KB |
sha256:d70a67be42296126de39d889b688452eb98893aea5bc723d1cd834af218a0f88
|
|
|
rust-sdk-windows-winml-logs
|
385 Bytes |
sha256:ff75075c046a8cd53b63f7d6e6518cd9089657a45ddd0831ae15aafc955195bd
|
|