extend id filter to support in #1276
nikgrafbuild-server.yml
on: pull_request
Build and Push
1m 41s
Annotations
1 error and 1 warning
|
Build and Push
buildx failed with: ERROR: failed to build: failed to solve: process "/bin/sh -c pnpm build && pnpm --filter server prisma generate && pnpm --filter server build && pnpm --filter server deploy --prod deployment --legacy && mkdir -p deployment/out && mv deployment/dist deployment/node_modules deployment/package.json deployment/out && mv deployment/prisma/generated/client/libquery_engine-linux-musl-arm64-openssl-3.0.x.so.node deployment/out/dist/libquery_engine-linux-musl-arm64-openssl-3.0.x.so.node && mv deployment/prisma/generated/client/libquery_engine-linux-musl-openssl-3.0.x.so.node deployment/out/dist/libquery_engine-linux-musl-openssl-3.0.x.so.node && mv deployment/prisma deployment/out" did not complete successfully: exit code: 1
|
|
Build and Push
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: docker/build-push-action@v6, docker/metadata-action@v5, docker/setup-buildx-action@v3, docker/setup-qemu-action@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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 | |
|---|---|---|---|
|
graphprotocol~hypergraph~XRU87G.dockerbuild
Expired
|
26.5 KB |
sha256:544c062d08d049a48e2cb6d0c14d60d445f160bdb4e865bb07168af7ffeb34a1
|
|