• Onebox v33.16.1
    Release / build-and-release (push) Failing after 16m51s
    Stable

    philkunz released this 2026-10-13 15:25:26 +00:00 | 14 commits to main since this release

    2026-10-13 - 33.16.1

    Fixes

    • Pin the platform Corestore 32.2.5 by its multi-platform image index code.foss.global/serve.zone/corestore@sha256:a6a702f04320e15198a16a309dd939af927d3bcd74d14d92b0ce3f44526a3e7d (linux/amd64 and linux/arm64), moved from 32.2.4 (sha256:5934215cc86c5b1d79fce5040a03341d7114abd00bc71329f255e76efc158aaf) in ts/platform-images.ts, and declare it as oneboxCorestorePinnedRelease 32.2.5. Corestore 32.2.5 is a maintenance release of the 32.2 line that moves @lossless.org/nosqldb from 10.6.1 to 10.10.0: a workload that dies inside a transaction no longer locks its successor out of new collections until its session expires (EFENCE_BUSY on create), and the engine spends far less CPU per command and at rest. A completed engine conversion keeps running the image its journal names, so after the binary upgrade it still runs 32.2.4 until onebox migration corestore-engine --replace-completed-target-image moves it, and a native owner until --replace-native-target-image does; both admit 32.2.4 to 32.2.5 as a newer release of the same major, read from both images' release labels; the 32.2.5 index states 32.2.5 in its org.opencontainers.image.version and version labels on both platforms. The completed-target replacement test now runs that move from the 32.2.4 index with this release's own pin. The move is one-way: NoSQLDB 10.10.0 opens a root 32.2.4 wrote in place, but once it has written, an engine before NoSQLDB 10.9 may not open that root again (Corestore 32.2.5 changelog), so take a block-level snapshot of the Corestore volume with the services stopped before the move. The change adds no startup data migration.

    Maintenance

    • release tooling: @git.zone/tstest 7.2.1, pnpm 12.10.0
    Downloads