• testing-19.0-4-20261016 9ed7a2b2fd

    testing-19.0-4-20261016 (debian-13-keel-lnmp_19.0-4_amd64.tar.zst)
    All checks were successful
    tests / package (push) Has been skipped
    tests / appliance (push) Successful in 12s
    tests / tests (push) Successful in 1m8s
    tests / stack (push) Successful in 2m38s
    Pre-release

    navigator released this 2026-10-16 21:02:36 -03:00 | 6 commits to main since this release

    Testing pre-release of 2026-10-16 (handbook decision 0059). Not for production. Version 19.0-4.

    Keel LNMP: nginx, MariaDB 11.8 and PHP-FPM 8.4 on Keel Web. The check page is https://

    /keel-check/.

    • Built on the build host from 9ed7a2b with keel-release, on Core 19.0-10 and Web 19.0-6 (keel-web 0.3.0). Packages: Debian 13 and archive.keellinux.org trixie-testing (keel 0.23.43).
    • keel 0.23.43 fixes keel#202: the first primary of a pair always came back from a cut as diverged, also when it took no write, because the copy that seeds the replica did not carry the binary log history of the primary (its first-boot GTIDs). A first primary that took no write now rejoins by GTID with no reseed. It also fixes keel#198 (the join names the failed step) and keel#201 (keel diff does not count a local sender as a replica).
    • Tested on real nodes across two sites: 2 CTs on BR1 and 1 CT on BR2, 3 etcd members, at base and under netem (250 ms, 25 ms jitter, 1.5 % loss). The first write came 0.3 to 1.9 s after the VIP moved, and 0 of 14583 acknowledged writes were lost. Evidence: docs/evidence/2026-10-17-lnmp-19.0-4-cross-site.md in Keel-Linux/handbook.
    • The sha512 file is signed by the main key and by the images key (decision 0055). Each key verifies it alone.
    Downloads