Release note - beVault 3.11

We are pleased to announce the release of beVault 3.11, bringing key improvements to query management, infrastructure flexibility, and user experience. This version focuses on giving users more control over generated SQL artifacts, extending the store ecosystem with Git support, and strengthening the reliability of the orchestration layer with Redis/Valkey enhancements.

Check out this release note to see what's new and stay tuned for new incoming releases in 2026 🚀

Rework of downloaded queries structure

beVault 3.11 significantly improves the structure of SQL artifacts generated and downloaded during version deployment. Following feedback from clients, both DDL and DML query files have been reorganized to make them easier to use with external tools and CI/CD pipelines.

• Split DDL files by source: The single DDL file containing all database schema changes is now split into multiple logical files, organized by source and object type — making it easier to apply targeted changes or integrate with source control workflows.

• Revised DML archive structure: Loading queries are now grouped and named according to a consistent convention, organized by source, data package, operation type, and load type — providing a clear, predictable structure for downstream automation.

• No impact on existing workflows: The deployment process in beVault remains unchanged — only the structure of the downloadable artifact is affected.

👉 Find more details about the new structure here: Deploy

GIT Store

beVault 3.11 introduces a new Git store type in the Workers solution, expanding the ecosystem of supported data endpoints. Workers can now connect to a Git repository as a physical store, enabling use cases where versioned files or configuration artifacts need to be retrieved or pushed as part of a data pipeline.

This new store type integrates fully with the centralized store management introduced in beVault 3.10 — it can be configured and managed directly from the States interface.

Redis / Valkey improvements

beVault 3.11 brings two important improvements to the Redis/Valkey layer powering the States orchestrator:

• TTL on execution-related keys: A configurable expiry time (default: one week) is now applied to all execution-related keys and hash entries in Redis/Valkey. This prevents executions from lingering indefinitely in case of abnormal termination, improving long-term reliability and keeping the cache clean. The timer can be adjusted or disabled via the RedisExecutionKeysMaxRetentionHours parameter, and a startup routine automatically applies any configuration changes retroactively to existing keys.

• Extended Redis/Valkey configuration flexibility: States can now connect to an externally hosted Redis/Valkey instance using a full connection string via the new RedisConfig parameter. This supports advanced setups such as managed cloud services with authentication, enabling deployments on infrastructure where a local Redis instance is not available.

Improved data package table loading (UI)

The Source module homepage now benefits from an optimized API to load staging tables more efficiently. This improvement reduces page load time and delivers a smoother, more responsive experience when navigating data packages with large numbers of staging tables.

List of changes

Query Structure

• DDL query file is now split into multiple files organized by source and object type

• DML archive structure revised with standardized naming and grouping conventions

Git Store

• New Git store type available in the Workers solution

• Manageable from the States centralized store interface

Redis / Valkey

• Added configurable TTL (RedisExecutionKeysMaxRetentionHours) on all execution-related keys and hash entries in Redis/Valkey

• Startup routine to retroactively apply TTL changes on existing keys

• Support for external Redis/Valkey via full connection string with authentication (RedisConfig parameter)

UI

• Improved datapackage table loading in the Source module homepage

Bug fixes

• Fixed Store manager crashing when EnvironmentName is empty

• Fixed stores in failed state not clearing their status when healthcheck is disabled

Components' version

Fix Versions