[Improvements🛠️]:Update tools directory, CI workflow, and dependencies for better compatibility and performance

[wind111-lang]

Changed tools/semver-check.js

Node.js 10 was end-of-life on December 31, 2021.
so using process.versions.node to always use the current Node.js version.
This change solves fix GitHub Actions test failures caused by specifying Node.js '10.12.0'. node-sqlite3 testing with Node.js 18, so '10.12.0' isn’t need.

Changed tools/BinaryBuilder.Dockerfile

• Fixed network connectivity issue during tests on bullseye with Node.js 18.
  Added --maxsockets=1 to npm install as a temporary workaround.
  This fixes the error: Client network socket disconnected before secure TLS connection was established in bullseye CI test.
  • I would like to propose updating our test environment from bullseye to Bookworm. This change aims to leverage the latest software versions, security patches, and performance improvements offered by Bookworm.

Changed workflow CI

• Improved Apple Silicon compatibility by specifying arm64 architecture for macos-latest.
  • Is macos-m1 test working in self-host-runner? If this change has problem, I undo macos-latest in arm64.
• Updated setup-msbuild from v1 to v2 for better Windows11 compatibility.
• Removed setuptools installation step because node-gyp v10 supports Python 3.12 by default.
• Keep current version of upload-artifact due to test failures with the latest version.

Upgrade some dependencies

• Updated node-addon-api to 8.0.0 or higher. (Update dependency node-addon-api to v8 #1767 )
• Updated tar to 7.0.0 or higher. (Update dependency tar to v7 #1777 )
• Updated node-gyp to 10 or higher. (Update dependency node-gyp to v10 - autoclosed #1724 )

These updates improve compatibility, performance, and security of your project.

[YasharF]

Hey there, I am curious, what kind of tests have run to verify the version bump is not creating other issues, regressions, etc. ?

[wind111-lang]

Hello, @YasharF.
Thank you for your comment.

I have run the workflow in this PR and passed all environments with the changes in semver-check.js and BinaryBuilder.Dockerfile. Since I'm running the workflow on a fork repository, I'm not sure what the results will be on master repository Actions.

The issue was that the version checked in semver-check.js was specified as Node 10, causing the tests to fail. Additionally, on Debian bullseye, the tests passed after temporarily setting maxsockets=1 to fix the Client network socket disconnected before secure TLS connection was established error.

After making these changes, I ran the workflow with the updated versions from the Renovate PR, and all environments passed successfully.

Thank you.

[netroy]

I ran the same test suite with this branch as I did in #1788, and everything worked as expected to me.

I get it if there are hesitations to merge these PRs, but it'd be nice to have a clarity on intent here, so that people like me can decide if we should wait for these PRs to be merged, or if we create a "temporary" fork to publish on NPM under a scope.

@daniellockyer can you please shed some light on the maintenance status of this project 🙏🏽

[wind111-lang]

Hello, there!

It’s been a few months—just checking in to see how things are going.
I totally understand things can get busy, so if this PR becomes ready to run CI again, feel free to let me know!

[netroy]

Just FYI folks, starting node 22.5, there is native sqlite support without having to worry about any external dependencies.
I've already started using that, and once node 24 is out (any time now), I'll stop supporting node 18/20 in my projects, and start using the native sqlite integration.
I already have a typeorm driver using the native sqlite API, that I plan to upstream soon.

Thanks a lot to the project maintainers for providing us with this very useful package for many years. I'm grateful.
But, I'll be unsubscribing from this PR now. 🙏🏽

[wind111-lang]

Thank you very much for providing the information!
I will go ahead and close this Pull Request.
Thank you for your support over the long term!