feat(node-sql): add SQL-based function template with example #160
docker.yaml
on: pull_request
Discover functions
3s
Matrix: build
Annotations
4 errors and 5 warnings
|
Build sql-example-fn
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c node --experimental-strip-types scripts/generate.ts && pnpm install --frozen-lockfile && pnpm --filter @constructive-io/sql-example-fn... build" did not complete successfully: exit code: 1
|
|
Build send-email-fn
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c node --experimental-strip-types scripts/generate.ts && pnpm install --frozen-lockfile && pnpm --filter @constructive-io/send-email-fn... build" did not complete successfully: exit code: 1
|
|
Build knative-job-example-fn
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c node --experimental-strip-types scripts/generate.ts && pnpm install --frozen-lockfile && pnpm --filter @constructive-io/knative-job-example-fn... build" did not complete successfully: exit code: 1
|
|
Build send-verification-link-fn
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c node --experimental-strip-types scripts/generate.ts && pnpm install --frozen-lockfile && pnpm --filter @constructive-io/send-verification-link-fn... build" did not complete successfully: exit code: 1
|
|
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 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 sql-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 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 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 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 knative-job-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 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 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 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 | |
|---|---|---|---|
|
constructive-io~constructive-functions~9HCRZB.dockerbuild
|
20.1 KB |
sha256:20a3191907420401f9abbf90a54d78f489d96e0a6b2533d7a817b492bf0a9f97
|
|
|
constructive-io~constructive-functions~JK4908.dockerbuild
|
19.5 KB |
sha256:ef89fd7070756d29fa7cf54cf88b9d518ea704145e94425ea65899c70d3c49e1
|
|
|
constructive-io~constructive-functions~OE7RCX.dockerbuild
|
20.5 KB |
sha256:78331db7531e3fbf02e54e3cc8ba046de3f27ac26ffa264eca1c4da2951cd2b6
|
|
|
constructive-io~constructive-functions~P2P2SE.dockerbuild
|
23.7 KB |
sha256:f3f24fb73f7b2ffd1d6cffc4d1065c2d7c952ee2f6254dc350cf84430d6a4f72
|
|
|
constructive-io~constructive-functions~SG2FHJ.dockerbuild
|
19.6 KB |
sha256:b0134b5f1494e029a6ad460501504b90d36a9c2d1c402b4d572c59dd174fe0f4
|
|