Skip to content

Version History

  • Changes

    Read the outcomes and fixes in this release.

  • Upgrade

    Check migration guidance before changing an existing deployment.

Check release changes before choosing an upgrade.

Find the relevant version below and check breaking changes before scheduling an upgrade.

Next: Upgrade guidance

Version v3.3.4 (2026-10-22)

This release fixes one startup failure in 3.3.3 and updates build and documentation tooling for known advisories. If you skipped a startup step to work around it, read the action under Fixed before you start 3.3.4.

Fixed

  • Startup no longer stops while cleaning up entry histories. When startup had to clean up entry histories that earlier resyncs had duplicated, Scribe could stop with Unable to discover event-stream normalization candidates, caused by Cannot change transaction read-only property in the middle of a transaction. We reproduced this failure: a new database connection reached Scribe with a transaction still open. New connections now start without one, which fixes the reproduced failure. Installations whose next start runs this cleanup, mostly the first start after an upgrade, may be affected. Action: if you skipped the cleanup by setting eventStreamNormalizationVersion in the subscriptions table, remove that marker right before the first start of 3.3.4, so the cleanup runs on that start:

    BEGIN;
    UPDATE subscriptions
    SET state = state - 'eventStreamNormalizationVersion'
    WHERE id LIKE 'identity-scribe:state:%';
    SELECT id, state ? 'eventStreamNormalizationVersion' AS marker_present
    FROM subscriptions WHERE id LIKE 'identity-scribe:state:%';
    COMMIT;

    Every row should show marker_present = false. After that start, the log reports the cleanup for each entry type and the marker is set again. Without the marker workaround, no action is needed.