3.3.1

Release notes for version 3.3.1 of the Rhize application.

Release date: 13 May 2026

Changes by service

The following sections document the changes this release brings to each service.

Admin

Releasing in step with other components.

BPMN engine

Releasing in step with other components.

Schema

Releasing in step with other components.

BAAS

Add

  • Add debug of pending transactions
  • Add extension to indexRebuild to support direct predicate rebuilds

Change

  • Change regexpcompare filter to process after indexed optimized filters by splitting filtering into two phases
  • Change badger library to latest
  • Change permissions/scopemap with updated Segment types
  • Change PendingTransaction to be renamed to PendingPostingTransaction for clarity

Fix

  • Fix atomic writes for split posting list rollups
  • Fix orphaned pending transactions during leadership changes
  • Fix querying pendingPostingTransactions under high load results in panic
  • Fix initialize CDC sentTs floor from snapshot ReadTs on startup

Core

Releasing in step with other components.

Agent

Change

  • Change to use forked gopcua library

Audit

Change

  • Change go.opentelemetry.io/otel to 1.40.0 from 1.37.0.

Keycloak Theme

Releasing in step with other components.

Router

Releasing in step with other components.

Compatibility

Rhize v3.3.1 has been tested to work with the following third-party applications:
  • Apollo router 1.61.0
  • Grafana: 10.0.0
  • Keycloak: 26.3.3
  • Keycloak Postgres: 17.6.0
  • Loki: 2.9.12
  • NATS: 2.10.25
  • Tempo: 2.7.1

Checksums

When you install, check the container images against these checksums:

Admin:
registry.gitlab.com/libremfg/frontend/libre-admin-ui:v3.3.1
sha256:dce5eb835a50c0a7b4c02eb81575b7666e44e53713d728285bc1165c0bcd053a

BAAS:
registry.gitlab.com/libremfg/baas:v3.3.1
sha256:64cae59a2381403753edfe83a5532296a392275a2093cb90f409cddcc35d45d8

BPMN Engine:
registry.gitlab.com/libremfg/bpmn-engine:v3.3.1
sha256:591466ed7aa33cd9eebbe15c8d379adcd49ce7ec7c3044ce7d9515ce8cf80fdc

Libre Core:
registry.gitlab.com/libremfg/libre-core:v3.3.1
sha256:bdfaf403aeeb205cc5328508fa73ac74b04a6d05c9e9820710dbba83976d94dc

Libre Agent:
registry.gitlab.com/libremfg/libre-agent:v3.3.1
sha256:08436b314cdaf9ce65ec01373b0237e94f7eda5d0a2d2f90646772b19306ab6b

Libre Audit:
registry.gitlab.com/libremfg/libre-audit:v3.3.1
sha256:ebe1d98310a5b1382bae3c0e2351996d3019722d86c8fdf3d4fcb153ba4038f1

Libre Audit Postgres:
registry.gitlab.com/libremfg/libre-audit/postgres:v3.3.1
sha256:f69c9ada24976f63f7f6276af91ceb14a8b517d1790346d65ada28150a8dd3ff

Libre Keycloak Theme:
registry.gitlab.com/libremfg/frontend/libre-keycloak-theme:v3.3.1
sha256:99de1a0b01a22ac9c2555f2154d406fa7fddd8af695372745eb4f68abca295a6

Libre Router Init:
registry.gitlab.com/libremfg/libre-router-init:v3.3.1
sha256:03de69e8318db0ff6e5eb6a76cf87ec40145942d2ff21fde7ed3749d1ac7bc4e

Download v3.3.1-checksums.txt

Upgrade

To upgrade to v3.3.1, follow the Upgrade instructions.

Breaking Changes

Improved Transaction Visibility (BAAS)

You can now inspect pending posting and Raft transactions directly through the GraphQL admin API. New types (PendingPostingTransaction, PendingRaftTransaction) and query endpoints give operators better tooling to diagnose stuck or orphaned transactions without needing direct database access.

Atomic Writes for Split Posting Lists (BAAS)

Split posting list updates are now written atomically, eliminating a class of subtle corruption bugs that could occur if a write was interrupted mid-way.

Targeted Index Rebuild (BAAS)

The index rebuild operation now accepts a predicate field directly, in addition to attribute. This allows more surgical index repairs to previously inaccessible structures like dgraph.type

Restore Procedure

With changes to BAAS, it is no longer possible to wait for a snapshot and have the database synchronize the data across. Instead, all Alpha replicas need to be initialized with the same backup.

For details, follow the GraphDB Restore instructions.