[SEA-NodeJS] (2/8) napi-rs binding consumer — TS loader + build script #926
msrathore-dbAnnotations
7 errors and 1 warning
|
check
Process completed with exit code 1.
|
|
check
Commit a63373b16e6459af84f0572664c7bdb3380b9b9b is missing a DCO sign-off
|
|
check
Commit e8aa20677bc8db5627e0d18dc192b8f5d160b861 is missing a DCO sign-off
|
|
check
Commit ec3e0c9504abe3d7db25de25e4357f15dec5e67f is missing a DCO sign-off
|
|
check
Commit 6a54b3a0ab8ab60d505e95e193e678e7a57217d9 is missing a DCO sign-off
|
|
check
Commit 2f1865be47f5737e4aa3a1be3303487d2ff2e7bb is missing a DCO sign-off
|
|
check
Commit 6b70ce415cfb9dec1508d309a7962b9141d1a45a is missing a DCO sign-off
|
|
check
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/github-script@d7906e4ad0b1822421a7e6a35d5ca353c962f410. 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/
|