dqlite v1.18.0

What's Changed

• Add an API for querying the last raft log entry by @cole-miller in #683
• Fix the build when liblz4 is missing and test it by @cole-miller in #693
• github: Test with musl by @cole-miller in #682
• Propagate raft_recover errors and improve tracing by @petrutlucian94 in #702
• Remove option to link separately-built libraft by @cole-miller in #690
• Remove dqlite-next build configuration by @cole-miller in #704
• Start instrumenting existing code with state machines by @cole-miller in #678
• Snapshot checkpointing by @marco6 in #710
• Refactor leader.c to fix stack growth in handle_exec_sql by @cole-miller in #697
• Fix frames leak when VfsPoll fails by @cole-miller in #713

Full Changelog: v1.16.7...v1.18.0

dqlite v1.17.1 LTS

This is a release in the v1.17.x LTS series. It exists only for technical reasons and there are no functional differences from v1.17.0.

dqlite v1.17.0 LTS

This is the first release of the dqlite v1.17.x LTS release series. This release series will incorporate fixes for security issues and possibly other major bugs at the maintainers' discretion. It will not see any new features or breaking changes. You can track this LTS release series by following the lts-1.17.x branch; ongoing development will continue on master.

Compared to the last non-LTS release (dqlite v1.16.7), this release contains:

• Add an API for querying the last raft log entry by @cole-miller in #683
• Fix the build when liblz4 is missing and test it by @cole-miller in #693
• github: Test with musl by @cole-miller in #682
• Propagate raft_recover errors and improve tracing by @petrutlucian94 in #702
• Remove option to link separately-built libraft by @cole-miller in #690
• Remove dqlite-next build configuration by @cole-miller in #704
• Start instrumenting existing code with state machines by @cole-miller in #678
• Snapshot checkpointing by @marco6 in #710
• Refactor leader.c to fix stack growth in handle_exec_sql by @cole-miller in #697
• Fix frames leak when VfsPoll fails by @cole-miller in #713

Full Changelog: v1.16.7...v1.17.0

dqlite v1.17.0 LTS (first release candidate)

This is a release candidate for dqlite v1.17.0, which will be the first release of the v1.17.x LTS series.

dqlite v1.16.7

This release contains three bug fixes:

• Fix a possible UAF by @zouyonghao in #669
• bugfix: reading segment, correctly stop on error by @letFunny in #672
• Cleanup prepared statement during node close by @marco6 in #675

See also the full list of commits.

Note that the v1.16.6 tag is flawed and should not be treated as a release, since (due to human error) it points to a commit for which the version numbers in configure.ac and dqlite.h still read 1.16.5. This release is functionally identical to the v1.16.6 tag and should be used instead.

dqlite v1.16.6

This release contains three bug fixes:

• Fix a possible UAF by @zouyonghao in #669
• bugfix: reading segment, correctly stop on error by @letFunny in #672
• Cleanup prepared statement during node close by @marco6 in #675

See also the full list of commits.

dqlite v1.16.5

Significant changes in this release:

• dqlite now uses file locking to ensure that two nodes don't run concurrently using the same data directory (#656).
• The minimum required version of libuv has been increased to 1.34 (#617).

This release also includes smaller bug fixes, plus new code (not yet enabled) related to the future move to storing databases and WALs on disk.

dqlite v1.16.4

This release fixes some bugs in dqlite's build system that were introduced when developing the --enable-build-raft option:

• Fix building without --enable-build-raft when liblz4 is not available: #603
• Fix building with vendored sqlite3.c: #607

It also introduces code for a new thread pool that will be used in future versions of dqlite, but is not currently enabled:

• #598

dqlite v1.16.3

This release brings a new option for dqlite's configure script, --enable-build-raft. When this option is passed, dqlite will build and use a private Raft implementation instead of linking to an external libraft. --enable-build-raft is the preferred way to use dqlite going forward, but linking to an external libraft remains supported for now, and is the default if the new flag is not passed.

One other internal change is included in this release:

• Fix many cases of arithmetic on void pointers (#569)

dqlite v1.16.2

This release brings a fix for using dqlite with SQLite versions greater than 3.45.0 (#564), plus:

• A more readable logging format (#542).
• An internal improvement to how dqlite reacts to Raft state changes (#545).
• A new dqlite_node configuration option to control snapshot compression (#567, thanks to new contributor @cnnrznn).