Skip to content

feat: compute usage logging (Phase 1 — billing/metering foundation) #228

feat: compute usage logging (Phase 1 — billing/metering foundation)

feat: compute usage logging (Phase 1 — billing/metering foundation) #228

Triggered via pull request June 12, 2026 06:00
Status Success
Total duration 4m 17s
Artifacts 5

docker.yaml

on: pull_request
Discover functions
4s
Discover functions
Build knative-job-service
4m 13s
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 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 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 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 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~6QJAK0.dockerbuild
41.5 KB
sha256:7ab5251dd89ef3ed02d05f709a1f038e868acde27820271b67547d8af8f71367
constructive-io~constructive-functions~QITVLZ.dockerbuild
40.1 KB
sha256:8710fdd9f21ac6ddb72dcb35efd3035a04dc4b0a2ab4222b24cbf069a635e08d
constructive-io~constructive-functions~RSCYOE.dockerbuild
39.9 KB
sha256:e0c7102eac2e564fba7bef5e27216ea40636e58d1d5373aa7db2d89d9d061518
constructive-io~constructive-functions~Y2K4L5.dockerbuild
39.9 KB
sha256:34943f030b8e72d017221a85cc6409f4df7cf07818a8013cad38c8f9160ba4c7
constructive-io~constructive-functions~ZQ2QDE.dockerbuild
25.2 KB
sha256:effa8e50d81d98aa942a869eb86718bcfeea14de1cc15e307f692187d8adac68