[github-actions]

The release check built and ran the tests against v26.9.0 and
they passed, so the engine can be adopted. This moves the pin
v26.7.3 → v26.9.0 in all three places that carry it:
update_libchdb.sh, build.rs, and engine under
[package.metadata.chdb] in Cargo.toml, which is what tells a user
of the published crate which engine is inside it.

https://github.com/chdb-io/chdb-rust/actions/runs/36533219125

Based on 20c25fa, the commit that run tested.

No checks will appear here. GitHub does not start workflow runs for
commits a workflow pushed with GITHUB_TOKEN, and running CI on this
branch would exercise the same tests against the same engine the check
just used.

Note

Move engine pin to v26.9.0

• Updates CHDB_ENGINE_PIN from v26.7.3 to v26.9.0 in Cargo.toml, build.rs, and update_libchdb.sh
• Restructures the direct-insertion branches in insert_record_batch_direct and insert_record_batch_reader in arrow_insert.rs to yield the connection call as the block result; fallback SQL paths remain conditionally compiled
• Risk: bumping the engine to v26.9.0 may change runtime behavior of the bundled ClickHouse engine; check CHDB_ENGINE_PIN consumers in build.rs

^{Macroscope summarized 7d9f5dd.}

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ ShawnChen-Sirius
❌ github-actions[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}