[Experimental] Support for prisma #4250
Annotations
3 errors and 5 warnings
Compile
@xata.io/prisma#build: command (/home/runner/work/client-ts/client-ts/packages/plugin-client-prisma) pnpm run build exited (1)
|
Compile
Expected 1 arguments, but got 2.
|
Compile
Process completed with exit code 1.
|
The following actions uses node12 which is deprecated and will be forced to run on node16: peter-evans/find-comment@v1, peter-evans/create-or-update-comment@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
Update existing comment with stale state of npm release
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Find Comment
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Find Comment
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
Find Comment
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
The logs for this run have expired and are no longer available.
Loading