Repository navigation
Changes since previous release
- Fixed issue #308 - In 64-bit WASM builds random number generation aborts. 32-bit WASM builds are not affected.
- Fixed issue #309 -
sqlite3_rekeydid not use the transient cipher parameter values, if the old and new cipher scheme were identical. Instead the default values were used. The expected behaviour has been restored. - Fixed issue #310 - Call
sqlite3OsFileControlHintinstead ofsqlite3OsFileControlto check whether a codec is in use. OnlySQLITE_TESTbuilds are affected
An update is recommended.
Details can be found in the change log and the commit history.
Release Summary
Important
📌 The amalgamation source package including configure is still experimental. 📌
Currently, only POSIX compliant systems are supported. Support files for building on Windows are included, but will only be adapted if the need arises.
Please report any issue you may experience using the GitHub issue tracker.
❗ Please share your experiences with this source package. TIA. ❗
Notes
This release contains the following precompiled binaries:
- SQLite3 binaries for Windows (SQLite3 shell and DLLs) with resp. without enabled ICU support in variants for 32-bit and 64-bit Windows. The SQLite3 shell applications support the SQLite Archive feature,
- Source code amalgamation (amalgamation) - a single C source file and a single C header file,
- Source code amalgamation (autoconf) - a single C source file and a single C header file - including a
configurescript for POSIX compliant systems, - Precompiled SQLite Android library (see SQLite Android Bindings),
- Precompiled bundles of
sqlite3.wasmand its JavaScript APIs, ready for use in web applications (see SQLite3 WebAssembly), in two variants:*-wasm.zip: baseline build, runs in any WebAssembly runtime,*-wasm-simd128.zip: build with WebAssembly SIMD128 enabled for better performance (e.g. for ChaCha20); requires a runtime with SIMD support (current versions of Chrome, Firefox, Safari and Node.js).
The variant is fixed at build time. Applications that need to support both should select the matching binary when loading the module, e.g. via feature detection (WebAssembly.validate()or the wasm-feature-detect library).
Verification
Release artifacts were built by GitHub Actions and are published with GitHub Artifact Attestations for provenance verification.
The SHA256SUMS file containing the checksums of the release artifacts is additionally signed using Sigstore Cosign.
To verify the integrity and authenticity of the checksum file, install Cosign and run:
cosign verify-blob \
--certificate sqlite3mc-2.7.1-SHA256SUMS.pem \
--signature sqlite3mc-2.7.1-SHA256SUMS.sig \
--certificate-identity-regexp '^https://github.com/utelle/SQLite3MultipleCiphers/.*' \
--certificate-oidc-issuer https://token.actions.githubusercontent.com \
sqlite3mc-2.7.1-SHA256SUMS