Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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@v4, actions/checkout@v4, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 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/

non-Sendable type 'duckdb_connection?' (aka 'Optional<UnsafeMutablePointer<_duckdb_connection>>') of property 'connectionHandleForInterrupt' cannot exit actor-isolated context; this is an error in the Swift 6 language mode

result of call to 'executeQuery' is unused

result of call to 'executeQuery' is unused

instance method 'unlock' is unavailable from asynchronous contexts; Use async-safe scoped locking instead; this is an error in the Swift 6 language mode

instance method 'lock' is unavailable from asynchronous contexts; Use async-safe scoped locking instead; this is an error in the Swift 6 language mode

capture of 'handle' with non-Sendable type 'UnsafeMutablePointer<DBPROCESS>' (aka 'UnsafeMutablePointer<dbprocess>') in a '@sendable' closure

capture of 'handle' with non-Sendable type 'UnsafeMutablePointer<DBPROCESS>' (aka 'UnsafeMutablePointer<dbprocess>') in a '@sendable' closure

capture of 'handle' with non-Sendable type 'UnsafeMutablePointer<DBPROCESS>' (aka 'UnsafeMutablePointer<dbprocess>') in a '@sendable' closure

initialization of immutable value 'length' was never used; consider replacing with assignment to '_' or removing it

left side of nil coalescing operator '??' has non-optional type '[String]', so the right side is never used