Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@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/

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

unused function 'is_array_buffer_value'

unused function 'visited_replacement'

unused function 'visited_matches'

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

function '_describe_export_name' is not needed and will not be emitted

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

unused variable 'resolver'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@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/

ignoring return value of function declared with 'warn_unused_result' attribute

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

ignoring return value of function declared with 'warn_unused_result' attribute

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@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/

unused function 'is_array_buffer_value'

unused function 'visited_replacement'

unused function 'visited_matches'

unannotated fall-through between switch labels

unused variable 'resolver'

function '_describe_export_name' is not needed and will not be emitted

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

unused function 'is_array_buffer_value'

unused function 'visited_replacement'

unused function 'visited_matches'

unannotated fall-through between switch labels

function '_describe_export_name' is not needed and will not be emitted

unused variable 'resolver'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, mymindstorm/setup-emsdk@v14. 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/

unused function 'is_array_buffer_value'

unused function 'restore_transfer_markers_impl'

unannotated fall-through between switch labels

unused variable 'resolver'

function '_describe_export_name' is not needed and will not be emitted

unused variable 'context'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, mymindstorm/setup-emsdk@v14. 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/

unused function 'visited_matches'

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *, int)') to 'JSCFunction *' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *, int)') to 'JSCFunction *' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *)') converts to incompatible function type

unannotated fall-through between switch labels

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *, int)') to 'JSCFunction *' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *, int)') to 'JSCFunction *' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *, int)') to 'JSCFunction *' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *, int)') to 'JSCFunction *' (aka 'unsigned long long (*)(JSContext *, unsigned long long, int, unsigned long long *)') converts to incompatible function type

function '_describe_export_name' is not needed and will not be emitted

unused variable 'resolver'

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

comparison of integers of different signs: 'int' and 'size_t' (aka 'unsigned long')

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

unannotated fall-through between switch labels

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

unused variable 'resolver'

function '_describe_export_name' is not needed and will not be emitted

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

unannotated fall-through between switch labels

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

unused variable 'resolver'

function '_describe_export_name' is not needed and will not be emitted

cast from 'JSValue (*)(JSContext *, JSValue, int, JSValue *, int)' to 'JSCFunction *' (aka 'JSValue (*)(JSContext *, JSValue, int, JSValue *)') converts to incompatible function type

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

ignoring return value of function declared with 'warn_unused_result' attribute

ignoring return value of function declared with 'warn_unused_result' attribute

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

ignoring return value of function declared with 'warn_unused_result' attribute

ignoring return value of function declared with 'warn_unused_result' attribute

'v8::HighAllocationThroughputObserver' has virtual functions but non-virtual destructor

'v8::ZoneBackingAllocator' has virtual functions but non-virtual destructor

'v8::JobDelegate' has virtual functions but non-virtual destructor

'v8::Context::DeepFreezeDelegate' has virtual functions but non-virtual destructor

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

declaration of 'class_info' hides previous local declaration

'resolver': local variable is initialized but not referenced

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/cache/save@v4, actions/setup-python@v5, actions/upload-artifact@v4, dsaltares/fetch-gh-release-asset@1.1.2. 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/

declaration of 'class_info' hides previous local declaration