Skip to content

feat(www): FlowsPanel UI — SDK migration, codegen bump, execution tables, icon fixes #296

feat(www): FlowsPanel UI — SDK migration, codegen bump, execution tables, icon fixes

feat(www): FlowsPanel UI — SDK migration, codegen bump, execution tables, icon fixes #296

Triggered via pull request June 14, 2026 04:39
Status Success
Total duration 3m 43s
Artifacts 5

docker.yaml

on: pull_request
Discover functions
4s
Discover functions
Build knative-job-service
3m 40s
Build knative-job-service
Matrix: build
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
Build python-example-fn
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 will be forced to run with Node.js 24 by default starting June 16th, 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 node-example-fn
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 will be forced to run with Node.js 24 by default starting June 16th, 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 send-email-fn
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 will be forced to run with Node.js 24 by default starting June 16th, 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 send-verification-link-fn
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 will be forced to run with Node.js 24 by default starting June 16th, 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 knative-job-service
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 will be forced to run with Node.js 24 by default starting June 16th, 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
constructive-io~constructive-functions~JV60FZ.dockerbuild
41 KB
sha256:6cdd5fea1cd99a5832ffd168f7a92de586d26a511d52d07d892613c6105991a1
constructive-io~constructive-functions~LHV0J4.dockerbuild
41.1 KB
sha256:97ad46c3cb0bb78e002d565edb0d6711b0e9ad133535eb55915ad8ad2c7493ae
constructive-io~constructive-functions~M4K96Y.dockerbuild
41.2 KB
sha256:1976478847cc22904adc7b08030c0053eff6712a18b7dad693cec0ac040d2843
constructive-io~constructive-functions~MBFGBK.dockerbuild
25 KB
sha256:ba627fa0c2b1ce30b13e4c95eb5658dbbfff1af70de7c476ccd9951578b5532d
constructive-io~constructive-functions~SZL59R.dockerbuild
40.9 KB
sha256:0217621911272cbe1fe1850d7a66452960bb1de67cf0e3fc924f40fd1b3834dc