-
Notifications
You must be signed in to change notification settings - Fork 0
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
npx ccg change --verify
works fine locally but fails in the github action: https://github.com/MFB-Technologies-Inc/react-async-renderer/blob/f3c59ba56b06d0618aa1bd3127b36ce2868cc9db/.github/workflows/build.yml#L32
- name: Verify change files
run: npx ccg change --verify
error
npx ccg change --verify
shell: /usr/bin/bash -e {0}
node:internal/process/promises:[3](https://github.com/MFB-Technologies-Inc/react-async-renderer/actions/runs/14539723546/job/40795159089?pr=79#step:5:3)89
new UnhandledPromiseRejection(reason);
^
UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "command failed with exit code 1".
at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)
at processPromiseRejections (node:internal/process/promises:[4](https://github.com/MFB-Technologies-Inc/react-async-renderer/actions/runs/14539723546/job/40795159089?pr=79#step:5:5)70:17)
at process.processTicksAndRejections (node:internal/process/task_queues:9[6](https://github.com/MFB-Technologies-Inc/react-async-renderer/actions/runs/14539723546/job/40795159089?pr=79#step:5:7):32) {
code: 'ERR_UNHANDLED_REJECTION'
}
Node.js v20.19.0
Error: Process completed with exit code 1.
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working